Repository navigation
Track work in GitHub issues instead of REVIEW-ISSUES.md - #290
Merged
Merged
Conversation
The open entries in REVIEW-ISSUES.md are now issues #267-#289, labelled by priority, type, status and area. CONTRIBUTING.md explains how to find, claim and link issues and what the labels mean; the overlap groups became Area: labels. The issue templates apply Type: and Status: Pending labels so new issues land in triage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
Summary
Moves issue tracking from
REVIEW-ISSUES.mdto GitHub issues.stateor PKCE (WEB-006)", so older branches, commits and PRs still match. The 8 fixed entries are covered by Fix Next.js advisories, 404-page SSRF and Discord guild leak #247, Stop .gitattributes from corrupting binary fonts (WEB-004) #248 and Keep one QueryClient and share the drugs query (WEB-007, WEB-029) #264, or by Update dependencies to their latest versions (WEB-026) #265 (WEB-026) and Pass the Keycloak client ID to next build (WEB-031) #266 (WEB-031).Priority:(P0–P3 map to Critical/High/Medium/Low),Type:,Status:andArea:label, plus tags such assecurity,performanceorgood first issue. The tracker's overlap groups becameArea:labels, because issues in the same area touch the same files.CONTRIBUTING.md: new sections on finding, claiming and linking issues and on the labels. They replace the tracker's working rules. The checks section now listsnpm test, which CI runs, and thenpm ci --ignore-scriptstip.Type: BugorType: EnhancementplusStatus: Pending, so new issues land in triage. The plainbugandenhancementlabels are no longer applied.src/app/not-found.tsx: the comment pointed at WEB-002 in the deleted file. It now cites Fix Next.js advisories, 404-page SSRF and Discord guild leak #247.#265 and #266 had both merged before this branch was cut, so their edits to
REVIEW-ISSUES.mdare included and no conflict arises. #266's follow-up (UAT composebuild.args) is recorded in #275.Type of change
Checklist
uat(this PR targetsuat, notmain)npx eslint .): checked the one changed source file, a comment-only editnpx next buildsucceeds locally (also type-checks): not run; no code changes beyond a comment.envvalues, or user data includedTest plan
npx prettier --check CONTRIBUTING.md: passes.npx eslint src/app/not-found.tsx: passes.git grep REVIEW-ISSUES: no references left.gh issue list.🤖 Generated with Claude Code