Repository navigation
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
|
||
| Before each closure, reread the live state, head SHA, recent commits, comments, reviews, labels, and holds. Recompute the decision if anything changed after inspection; do not close on a stale snapshot. If new activity is ambiguous, leave it for review. | ||
|
|
||
| Use `gh pr close <number> -R github/opensource.guide` with a brief, welcoming closure comment explaining the specific unfinished work and the last substantive update date. Invite a completed follow-up or reopening when work resumes. Do not call the contribution "naive", speculate about intent, or imply that the contributor is unwelcome. Do not delete the branch. |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The triage procedure still has two active documentation issues: its prescribed close command omits the required explanatory comment, and its listing command may omit pull requests and the review data needed for complete triage.
2 open issues
What changed in this PR
Adds a repository-specific PR triage skill for evaluating contributions, translations, CI status, and stale translation pull requests in github/opensource.guide.
Changes:
- Defines evidence-based review guidance using repository contribution, translation, content, style, and persona documentation.
- Documents PR inspection, CI reporting, approval safeguards, and contributor communication.
- Adds a guarded 60-day cleanup workflow for clearly incomplete translation PRs.
| File | Description |
|---|---|
| .github/skills/pr-triage/SKILL.md | Introduces the complete repository-specific pull request triage workflow, including translation assessment, CI guidance, reporting requirements, and stale cleanup procedures. |
Review effort: Lite (dynamic)
|
|
||
| ## Inspection workflow | ||
|
|
||
| 1. Use `gh pr list -R github/opensource.guide --state open` with sufficient pagination to cover the queue. Collect author, body, labels, draft state, base branch, head SHA, changed files, reviews, comments, and `statusCheckRollup`. Do not change branches or disturb local changes. |
|
|
||
| Before each closure, reread the live state, head SHA, recent commits, comments, reviews, labels, and holds. Recompute the decision if anything changed after inspection; do not close on a stale snapshot. If new activity is ambiguous, leave it for review. | ||
|
|
||
| Use `gh pr close <number> -R github/opensource.guide` with a brief, welcoming closure comment explaining the specific unfinished work and the last substantive update date. Invite a completed follow-up or reopening when work resumes. Do not call the contribution "naive", speculate about intent, or imply that the contributor is unwelcome. Do not delete the branch. |
tomthorogood
approved these changes
Nov 13, 2026
tomthorogood
left a comment
tomthorogood
left a comment
Contributor
There was a problem hiding this comment.
Seems good to me. I like the explicit details pertaining to translations and long-running work. Thanks for putting this together.
|
|
||
| ## Goal and sources | ||
|
|
||
| Help maintain the Open Source Guides with evidence-based recommendations and a welcoming contributor experience. Prefer human review whenever approval or closure is borderline. Do not equate unfamiliar language, small changes, failing CI, or age alone with a low-quality contribution. |
|
|
||
| Recognize Dependabot by its actual bot identity (`dependabot[bot]`, sometimes displayed as `app/dependabot`), not a similar human login. Treat routine dependency updates and verified repository-owned automation as normal maintenance, not external promotional submissions. | ||
|
|
||
| Recommend ✔️ for a routine, in-scope bot change only when its current diff is appropriate and applicable checks pass. Major upgrades, unexpected files, changed permissions, failing or missing checks, or uncertain automation provenance require 🔍. A `github-` prefix alone does not establish trust. Bot status never authorizes approval, merge, or CI execution. |
| - `_articles/<locale>/` should contain translations of the current guides, preserving front-matter field names and functional metadata, Liquid expressions, HTML structure, code examples, links, and anchors. | ||
| - Follow the documented removal of the `untranslated` field when content is translated. Removing a marker without translating the content is not completion. | ||
| - The locale's `index.html` should follow the root index with the documented `lang` and `permalink` changes; other front-matter values should remain unchanged. | ||
| - Look for missing guides or strings, copied English presented as finished translation, placeholder text, mismatched language codes, malformed front matter, broken internal links, and changes to shared templates that merely hide incomplete content. |
This branch has not been deployed
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.
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.
Adds a PR triage skill, based on the one for github/explore , to help maintainers work through the PR backlog