[OPS-1301] Delete legacy capabilities_and_config.yaml (duplicate) - #91
Merged
Conversation
…enerate-baton-metadata.yaml) This repo already has generate-baton-metadata.yaml (managed by baton-admin) which generates the same baton_capabilities.json + config_schema.json output. The legacy capabilities_and_config.yaml is a duplicate that auto-commits to main with the long-lived RELENG_GITHUB_TOKEN PAT — both unwanted now that OPS-1300 is in place. Linear: https://linear.app/ductone/issue/OPS-1301 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Claude finished @ennyjfrick's task in 33s —— View job PR Review: Delete legacy
|
| Aspect | Legacy (deleted) | Modern (kept) |
|---|---|---|
| Trigger | push to main |
push to main + pull_request |
| Auth | RELENG_GITHUB_TOKEN secret |
baton-ci app token |
| Build + generate | go build → config + capabilities |
Same |
| Commit outputs | EndBug/add-and-commit@v9 |
Same |
| PR validation | ❌ | ✅ (metadata freshness + docs check) |
Both workflows generate the same two files (config_schema.json, baton_capabilities.json) and commit them with the same message. Having both fire on push to main would indeed cause redundant runs or race conditions on the commit step.
No concerns — safe to merge.
gontzess
approved these changes
May 4, 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.
Why
This repo already has
.github/workflows/generate-baton-metadata.yaml(the modern baton-admin-managed metadata workflow that already usesbaton-ci/baton-depsapp tokens after OPS-1300). The legacycapabilities_and_config.yamlruns the same generator separately, auto-commits the same files (baton_capabilities.json,config_schema.json) tomain, and still referencesRELENG_GITHUB_TOKEN.Two workflows pushing the same files to
maincauses redundant runs at best and merge conflicts at worst. Delete the legacy one.What
Removes
.github/workflows/capabilities_and_config.yaml. The moderngenerate-baton-metadata.yamlcontinues to do the same job.Linear: OPS-1301
🤖 Generated with Claude Code