LearnNewsExamplesServices
Frontmatter
titledocs: Enforce ''Resolves'' keyword for automatic PR closure (#9859)
authortobiu
stateMerged
createdAtApr 10, 2026, 12:13 PM
updatedAtApr 10, 2026, 12:14 PM
closedAtApr 10, 2026, 12:14 PM
mergedAtApr 10, 2026, 12:14 PM
branchesdev ← agent/9859-enforce-resolves-keyword
urlhttps://github.com/neomjs/neo/pull/9860
Merged
tobiu
tobiu commented on Apr 10, 2026, 12:13 PM

Updates the ticketing protocol and PR templates to mandate the Resolves #[ID] string, ensuring GitHub closes the target issues upon merge securely. Resolves #9859.

tobiu
tobiu commented on Apr 10, 2026, 12:13 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ # PR Review Summary

Status: Approved

Excellent update. Catching the fact that Closes didn't correctly trigger github's auto-close inside #9856 was crucial. Specifying Resolves explicitly saves a huge amount of manual tracking work. Let's merge!


πŸ“Š Evaluation Metrics

  • [ARCH_ALIGNMENT]: 100 - Maintaining a clean state across GitHub tracking objects is necessary for the graph.
  • [CONTENT_COMPLETENESS]: 100 - Both the PR Template and the Core Guidelines have been updated accurately.
  • [EXECUTION_QUALITY]: 100 - Clean markdown modifications.
  • [PRODUCTIVITY]: 100 - The primary goal of standardizing the Resolves keyword has been achieved.
  • [IMPACT]: 60 - Medium impact, specifically fixing issue pipeline hygiene.
  • [COMPLEXITY]: 10 - Highly isolated, simple documentation changes.

πŸ•ΈοΈ Context & Graph Linking

  • Target Epic / Issue ID: Resolves #9859
  • Related Graph Nodes: [Agent_Core_Guidelines], [Ticketing_Protocol]

🧠 Graph Ingestion Notes

  • [RETROSPECTIVE]: Consistently enforcing the exact GH keyword triggers is vital when bridging autonomous agent networks with legacy tracking systems. Always verify that GitHub receives the correct literal string.

πŸ“‹ Required Actions

Code perfectly reflects what was discussed. Ready for merge.