feat(repo): manage description and topics as code - #55
Merged
Conversation
The GitHub repository description still advertised Ubuntu 24.04 while the devcontainer moved to Ubuntu 26.04. Capture the description, topics and merge settings in .github/settings.yml so this metadata is version controlled and reviewable rather than drifting silently. Scoped to metadata only; no branches: block, so existing branch protection is untouched.
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The configuration would unintentionally disable currently enabled repository features.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds Settings GitHub App configuration to manage repository metadata and documents the new file.
Changes:
- Defines description, topics, and merge settings.
- Updates the repository layout documentation.
- Requires preserving existing wiki/projects settings and correcting the misleading trigger description.
File summaries
| File | Review |
|---|---|
AGENTS.md |
Documents the new settings file. |
.github/settings.yml |
Adds repository settings as code. Must avoid unintentionally disabling wiki/projects; trigger comment also needs correction. |
Review details
Suppressed comments (1)
.github/settings.yml:4
- The app does not apply settings on every default-branch push; it returns unless
.github/settings.ymlwas added or modified. Reword this trigger description so operators are not led to expect unrelated pushes to reconcile manual metadata drift.
# Applied by the "Settings" GitHub App (https://github.com/apps/settings)
# on every push to the default branch. If the app is not installed on this
# repository, this file is inert and metadata must be set manually
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
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.
Problem
The GitHub repository description was stale:
The devcontainer has been on Ubuntu 26.04 for a while (
.devcontainer/Dockerfile, README "Features"). Topics were also empty.Change
Adds
.github/settings.ymlso repo metadata is version controlled and reviewable instead of drifting silently:devcontainer,codespaces,ubuntu,template,opencode,claude-codeAlso lists the new file in the AGENTS.md repository-layout tree.
Deliberately scoped to metadata — there is no
branches:block, so existing branch protection rules are untouched.Caveat
This file only takes effect if the Settings GitHub App is installed on the repo. I could not verify installation (
/installationrequires an App JWT). The live description has been corrected directly viagh repo editso it is accurate regardless; this file is the durable source of truth going forward.Validation
Passes. Not a workflow file, so the SHA-pinning rule does not apply.