Repository navigation
fix: replace all topics so dropped topics are removed - #78
Merged
Merged
Conversation
Topics were only added with gh repo edit --add-topic, so a topic
removed from the input stayed on the repository. Set the full list
with PUT repos/{owner}/{repo}/topics instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
030
approved these changes
Oct 10, 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
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 and why
Up to now topics were applied with
gh repo edit --add-topic. That only adds topics, so a topic removed from thetopicsinput stayed on the repository, and the repository no longer matched the config.The step now calls
gh api -X PUT repos/$PROJECT/topicswith one-f names[]=<topic>per topic. This replaces all repository topics with exactly the list in the input.Behaviour change: topics on the repository that are not in
topicsare now removed. This is noted indocs/inputs.md.Testing
action.ymlparses as YAML, andbash -npasses on the extracted step script.ghand checked that it passes-f names[]=...once per comma-separated topic.GH_DEBUG=api gh api -X PUT repos/030/does-not-exist-zz9/topics -f 'names[]=a' -f 'names[]=b-c'to a repository that does not exist (it returned 404, so nothing changed). The debug output showed the body is a JSONnamesarray.general/PR-validation checks on this fork end instartup_failurebecause the fork's Actions policy blocksschubergphilis/*actions. That happens on every PR here, not because of this change.Closes #67
🤖 Generated with Claude Code