Scope WORKFLOW.md D1.6's secrets.json Pointer to Applicable Repos

[ptr727]

Summary

• D1.6 pointed at spec/secrets.json typeMechanisms as a bare "see" instruction. A source-only or other-type repo's own adapted copy carries baseline alone (per docs/repo-config.md, unchanged in shape by Host Repository Configuration Only in the Hub #861's hub-only repo-config/ move), so the pointer reads as actionable in a repo where the key never exists.
• Anchored the pointer to "that repo" (the C# or Python repo with tests D1.6 already scopes to), so the same sentence reads correctly whether or not the reader's own copy carries the key.

Verification

• scripts/prose_lint.py --diff origin/develop: 0 issues
• scripts/repo_gate.py: 0 issues (eol, eol-coverage, sha-pin)
• markdownlint-cli2 WORKFLOW.md: 0 issues
• Re-checked the issue's claim against current main (a week old): the underlying carry pattern it describes is unchanged by Host Repository Configuration Only in the Hub #861 (repo-config-carry.md renamed to repo-config.md, repo-config/ made hub-only, but spec/secrets.json's per-repo adapted-copy shape, including the source-only baseline-only case, is unchanged in substance).

Fixes #728.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated workflow guidance for C# and Python repositories that include tests.
  • Coverage requirements must now be declared in each repository’s coverage configuration under the appropriate mechanism entry.
  • Replaced the previous generic configuration reference with a repository-specific requirement, helping ensure coverage settings are clearly defined and consistently applied.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 398ba8fc-e52a-4f54-82dd-d11382015c05

📥 Commits

Reviewing files that changed from the base of the PR and between b02170d and 3ce9357.

📒 Files selected for processing (1)

• WORKFLOW.md

Included review availability: Your plan provides up to 10 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

D1.6 now directs C# and Python repositories with tests to define Codecov requirements in their own spec/secrets.json typeMechanisms entry.

Changes

Workflow requirement clarification

Layer / File(s)	Summary
Update the D1.6 specification reference WORKFLOW.md	D1.6 now references each repository’s own spec/secrets.json typeMechanisms entry for Codecov requirements.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 3ce93

This change only clarifies the scope of a documentation pointer, with no production behavior impact; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the WORKFLOW.md D1.6 pointer update and its repository scope.
Linked Issues check	✅ Passed	The change updates D1.6 to reference typeMechanisms only in applicable C# and Python repositories with tests, as required by issue #728.
Out of Scope Changes check	✅ Passed	The pull request changes only the requested WORKFLOW.md wording and does not modify unrelated files or D1.6 applicability requirements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-workflow-d1-6-secrets-pointer

---

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

PR Summary by Qodo

Clarify WORKFLOW.md D1.6 Codecov secret pointer is repo-scoped

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Clarify D1.6 Codecov secret requirement is scoped to C#/Python test repos.
• Avoid implying every repo’s carried spec/secrets.json has typeMechanisms.

Diagram

graph TD
  A(["Reader"]) -->|"reads"| B["WORKFLOW.md D1.6"] -->|"scopes to"| C["C#/Python repo"] -->|"references"| D["secrets.json typeMechanisms"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Link to repo-config carry rules

• ➕ Gives readers direct context on why some repos omit typeMechanisms
• ➖ Adds another conceptual hop; may be overkill for a single D1.6 sentence

2. Add an explicit example repo reference

• ➕ Removes ambiguity by pointing to a concrete C# or Python repo as an exemplar
• ➖ Examples can go stale if repo names/structure change

Recommendation: Current approach (scoping the sentence to “that repo’s own spec/secrets.json”) is the best balance: it fixes the misleading universality without adding more cross-doc dependencies or brittle examples.

Files changed (1) +1 / -1

Documentation (1) +1 / -1

WORKFLOW.mdScope D1.6 'spec/secrets.json' pointer to applicable repos +1/-1

Scope D1.6 'spec/secrets.json' pointer to applicable repos

• Refines the D1.6 wording to clarify that the 'typeMechanisms' check is against the C# or Python repo’s own carried 'spec/secrets.json', not universally present in every repo. Prevents readers in source-only/other repo types from interpreting the instruction as actionable when the key is absent.

WORKFLOW.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can commit Qodo's fix in one click with committable suggestions (GitHub & GitLab)

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[Copilot]

🟡 Changes recommended

The updated sentence still references typeMechanisms without explicitly noting that some adapted spec/secrets.json copies intentionally omit it, so the original downstream ambiguity is not fully resolved.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates WORKFLOW.md D1.6 to better scope the spec/secrets.json typeMechanisms reference so it reads correctly in downstream repositories whose adapted spec/secrets.json may not carry that key.

Changes:

• Reword D1.6’s applicability pointer from a generic “see typeMechanisms” to “per that repo’s own typeMechanisms entry”.

File summaries

File	Description
WORKFLOW.md	Rewords the D1.6 Codecov requirement to better scope the spec/secrets.json pointer to applicable repos.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟢 Approval recommended

The update is a targeted documentation clarification consistent with the documented adapted spec/secrets.json shapes and resolves the reported ambiguity without introducing new contract assertions.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0 new
• Review effort level: Lite