Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
42c630d
Require immutable code permalinks in issue triage comments
sergiou87 Sep 2, 2026
6af8251
Add first-pass root cause analysis to issue triage
sergiou87 Sep 2, 2026
435c0c0
Require independent evidence review during issue classification
sergiou87 Sep 2, 2026
dd09e6c
Supply author identity for cross-author spam detection
sergiou87 Sep 2, 2026
3320abc
Enable command-specific labels in automated issue triage
sergiou87 Sep 2, 2026
6ee9d97
Judge issue spam by maintainer relevance instead of author identity
sergiou87 Sep 2, 2026
6cdb7cb
Make the local command label allowlist authoritative
sergiou87 Sep 2, 2026
9f4df56
Disambiguate executable support from library design advice
sergiou87 Sep 2, 2026
20d09ea
Add paired regression coverage for Go library issue triage
sergiou87 Sep 2, 2026
23b5607
Detect verbatim reposts during issue spam triage
sergiou87 Sep 2, 2026
b169e71
Limit discussion provenance checks to explicit source links
sergiou87 Sep 2, 2026
87cb90f
Add regression coverage for attributed discussion reposts
sergiou87 Sep 2, 2026
6670514
Restrict repost detection to explicit source attributions
sergiou87 Sep 2, 2026
01ce729
Make attributed repost verification resilient to unsupported sources
sergiou87 Sep 2, 2026
167a24e
Use a verifiable source excerpt in the legitimate repost case
sergiou87 Sep 2, 2026
a23f348
Keep spam provenance policy in the evaluated shared criteria
sergiou87 Sep 2, 2026
71e2148
Require confirmed source matches before closing attributed reposts
sergiou87 Sep 2, 2026
b4b7c3c
Scope failed source verification to the provenance criterion
sergiou87 Sep 2, 2026
c4bffba
Isolate attributed provenance behavior with a metamorphic eval pair
sergiou87 Sep 2, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Require immutable code permalinks in issue triage comments
Ensure every source-code reference in an automated triage comment links to exact lines at a full commit SHA. This keeps technical claims verifiable after trunk changes and avoids forcing maintainers to locate referenced code manually.

Regenerate the compiled issue-triage workflow with gh-aw v0.87.5.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  • Loading branch information
sergiou87 and Copilot committed Sep 2, 2026
commit 42c630dbcba74f19822327e412c6223047401048
2 changes: 1 addition & 1 deletion .github/workflows/issue-triage.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 4 additions & 0 deletions .github/workflows/issue-triage.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,10 @@ explaining which label(s) you are suggesting (if any) and why, in plain language
duplicate, name the likely original. If you are suggesting no label, say so and state what
information would help a first responder finish triage.

When referring to source code, link every file, symbol, or line claim to an immutable
GitHub permalink pinned to a full commit SHA and exact line range. Do not use branch
links, bare file paths, or unlinked code references.

When calling `add-comment`, explicitly set `item_number` to
${{ github.event.issue.number || inputs.issue_number }}.

Expand Down