Repository navigation
chore: drop learn-ai from Doof - #507
Merged
Merged
Conversation
learn-ai now releases through the Concourse release-resource workflow and the /doof slash command in ol-infrastructure. Leaving it here would let `@doof release` cut a release-candidate branch that no pipeline deploys. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PSvo3NqRuCSJnK4j3DZCfm
feoh
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are the relevant tickets?
Companion to mitodl/ol-infrastructure#5838. Part of mitodl/hq#7185.
Description (What does it do?)
Removes the
learn-aientry fromrepos_info.json, so Doof no longer manages learn-ai releases.mitodl/ol-infrastructure#5838 moves learn-ai to the Concourse release-resource workflow, driven by the
/doofslash command in the new release bot. After that, therelease-candidatebranch Doof cuts is no longer watched by any pipeline, so a@doof releasefor learn-ai would produce a release nothing deploys.Config only; no Python changes.
How can this be tested?
Loaded the edited file through
lib.load_repos_info: 16 entries load (down from 17), andlearn-aiis not among them. A search of the repo finds no remaininglearn-aireferences.Additional Context
Merge after mitodl/ol-infrastructure#5838. Merging this first leaves learn-ai with no working release path until that one lands.
The
product-learn-aichannel is shared with the new release bot, so it stays as it is.🤖 Generated with Claude Code
https://claude.ai/code/session_01PSvo3NqRuCSJnK4j3DZCfm