Align settings.yml with the current repo template - #77
Merged
Conversation
This repo was still on the older settings.yml shape. Bring it up to date with what newer repos (docker-borgmatic, docker-rickroll, docker-starwars, crowdsec-troubleshooter, DefaultRepo) use: - Add name, has_discussions - Flip allow_merge_commit to true, add delete_branch_on_merge and allow_update_branch (matching the current default merge policy) - Clean up label color quoting and fix the wontfix color (bare hex, no leading '#', which the Settings app was silently dropping) Repo-specific description/homepage/topics unchanged.
1 task
modem7
added a commit
to borgmatic-collective/pypi
that referenced
this pull request
Jul 20, 2026
.github/settings.yml was an unedited copy of cibuildwheel's old settings file — still described this repo as "CIBuildWheel" with a homepage pointing at modem7's personal Cloudsmith "wheels" repo, and (more importantly) had default_branch: master, which doesn't exist here (this repo's actual default branch is main). - name/description/homepage/topics now describe this repo and point at borgmatic-collective's actual Cloudsmith repo - default_branch corrected to main - Brought structure in line with the current template (same as modem7/cibuildwheel#77): has_discussions, delete_branch_on_merge, allow_update_branch, allow_merge_commit: true, cleaned-up label color quoting, fixed wontfix color
2 tasks
grantbevis
pushed a commit
to borgmatic-collective/docker-borgmatic
that referenced
this pull request
Jul 20, 2026
This repo has no Settings app config at all (unlike cibuildwheel and pypi, both recently aligned to a common template — modem7/cibuildwheel#77, borgmatic-collective/pypi#85). Adding one here for consistency, and so there's something to actually investigate against in borgmatic-collective/pypi#86 (which found the app doesn't seem to be applying settings.yml on pypi either). Values reflect the live repo where I could check them (has_wiki, has_projects, and has_discussions are all on here, unlike the smaller repos, so left them on) and the README's current Docker Hub image (b3vis/borgmatic — the old modem7/borgmatic-docker link is stale). Topics and merge-option defaults match the shared template.
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
1 participant
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.
Summary
.github/settings.ymlwas still on an older shape. Brought it in line with what other repos (docker-borgmatic, docker-rickroll, docker-starwars, crowdsec-troubleshooter, DefaultRepo) currently use:name,has_discussions,delete_branch_on_merge,allow_update_branch,allow_merge_commit: true, and cleaned-up label color formatting (including thewontfixcolor, which had a leading#that the Settings app was silently dropping).description,homepage, andtopicsleft untouched.Test plan