Repository navigation
chore(github): issue forms, Dependabot labels, and label scheme docs - #311
Merged
Merged
Conversation
… docs Move issue kind to the org's Issue Types (Bug/Feature/Task) and document the area/ label scheme in CONTRIBUTING.md. Issue forms set the Issue Type and apply needs-triage; blank issues are disabled. Dependabot labels are set explicitly so it stops recreating python/github_actions labels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The label documentation contains invalid paths, a broken anchor, and an undefined Issue Type policy for questions.
Review effort: Balanced
Findings: 3
Open (3)
What changed in this PR
Adds structured issue intake and documents the repository’s new label scheme.
Changes:
- Adds Bug, Feature, and Question issue forms.
- Configures explicit Dependabot labels.
- Updates contributor and roadmap documentation.
| File | Description |
|---|---|
.github/ISSUE_TEMPLATE/bug_report.yml |
Adds structured bug reporting. |
.github/ISSUE_TEMPLATE/feature_request.yml |
Adds feature request intake. |
.github/ISSUE_TEMPLATE/question.yml |
Adds a question form. |
.github/ISSUE_TEMPLATE/config.yml |
Disables blank issues and adds contact information. |
.github/dependabot.yml |
Assigns dependency and CI/CD labels. |
CONTRIBUTING.md |
Documents issue types and labels. |
ROADMAP.md |
Links directly to the feature request form. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Fix the Dependabot cross-reference anchor, use full src/datasure/ paths in the area label table, and document that questions carry no Issue Type. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
NKeleher
approved these changes
Oct 6, 2026
NKeleher
left a comment
NKeleher
left a comment
Contributor
There was a problem hiding this comment.
Looks good to me! Will be very helpful to have these templates
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.
Pull Request Summary 🚀
What does this PR do? 📝
Adds the repository-side pieces of the label cleanup:
.github/ISSUE_TEMPLATE/). Bug and Feature forms set the org Issue Type; all forms applyneeds-triage. Blank issues are disabled and a contact link points to researchsupport@poverty-action.org.labels:in.github/dependabot.yml:dependencieson every ecosystem, plusarea/ci-cdon GitHub Actions updates.CONTRIBUTING.mddocumenting the scheme, and fixes to the stale "use GitHub Discussions" line (Discussions are disabled).ROADMAP.mdnow links to the feature request form instead of telling users to apply theenhancementlabel.Why is this change needed? 🤔
The repo has 23 labels. Several overlap (
Feature/enhancement/task,release-1.0vs the v1.0.0 milestone), several are unused, and 15 issues have no label because there are no issue templates. The org already has Issue Types (Bug/Feature/Task), so the kind of work moves there and labels cover only area and cross-cutting concerns.How was this implemented? 🛠️
Config and docs only. After this merges, the live label changes are made with
gh: renameUI/documentation/testing/ci-cd/Performanceto the new names, create the newarea/*andneeds-triagelabels, moverelease-1.0issues to the v1.0.0 milestone, set Issue Types on open issues, delete the retired labels, and close/unpin #145 (its guidance now lives in the bug form).Dependabot ignores labels that don't exist, so
area/ci-cdtakes effect once that label is created.How to test or reproduce ? 🧪
just pre-commit-runpasses.needs-triage.Screenshots (if applicable) 📷
N/A
Checklist ✅
🤖 Generated with Claude Code