Skip to content

Test: verify Copilot wire-up fires on contract-sensitive path#10

Open
Thiyaghessan wants to merge 1 commit into
mainfrom
test/copilot-review-trigger
Open

Test: verify Copilot wire-up fires on contract-sensitive path#10
Thiyaghessan wants to merge 1 commit into
mainfrom
test/copilot-review-trigger

Conversation

@Thiyaghessan
Copy link
Copy Markdown
Collaborator

Summary

Adds a single comment line at the top of `R/master_bmf_builder.R` naming the `bmf-master` contract it produces against. Content change is trivial; the real purpose is to verify that the Copilot code-review wire-up configured by the recently-added `.github/copilot-instructions.md` actually fires on a contract-sensitive file path.

What we're testing

Per the instructions file, the Copilot agent should:

  • Recognize `R/master_bmf_builder.R` as a contract-sensitive path (it's the BMF master publish path).
  • Read `nccs-contracts/contracts/bmf-master.yml` and the listed ADRs (0001, 0004, 0005, 0013, 0014) for context.
  • Leave a review comment that explicitly references the contract or one of those ADRs.

If a review appears with that shape, the wire-up is working. If no review appears (or it's a generic "looks fine" comment with no contract awareness), we need to check the org-level Copilot settings.

Disposition

This PR is for testing the Copilot wire-up only. The added comment is a harmless documentation improvement, but the intent is to close (or merge — your call) once the test conclusion is recorded.

🤖 Generated with Claude Code

Names the bmf-master contract at the top of the file so future
readers (humans and the Copilot review agent) know which contract
this file produces against. Test change for verifying that the
Copilot review wire-up from .github/copilot-instructions.md fires
on a contract-sensitive path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant