Skip to content

fix(docs): list the contributing guide where it actually lives - #80

Merged
hyperpolymath merged 4 commits into
mainfrom
fix/contributing-guide-content
Sep 19, 2026
Merged

hyperpolymath merged 4 commits into
mainfrom
fix/contributing-guide-content

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Sep 19, 2026 •

Copy link
Copy Markdown
Owner

The "Repository Structure" block still listed CONTRIBUTING.md at the repository root, but the guide lives at .github/CONTRIBUTING.md — the entry pointed at a location it had already moved away from.

This is the only change: the entry moves under the tree's existing .github/ branch, at the block's own comment column. The tree already rendered correctly and its layout is untouched.

Placeholder tokens in the block resolve to real values.


The contributing guide was instantiated from the estate template and kept one of the template's tokens verbatim: {{MAIN_BRANCH}}, in

  1. Check if it's already fixed in {{MAIN_BRANCH}}

The token is correct in the template itself, but a reader of this repository sees it literally. It resolves to this repository's default branch. One token — nothing else in the guide changes.

Mechanical repairs to the guide, each anchored on a known-broken form:

- substituted {{FORGE}}
- substituted {{OWNER}}
- substituted {{REPO}}

No prose is rewritten; only the broken forms are corrected.
@coderabbitai

coderabbitai Bot commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: b1a10d54-2833-43b7-a866-71075614934a

📥 Commits

Reviewing files that changed from the base of the PR and between 96f690f and a3c3452.

📒 Files selected for processing (1)
  • .github/CONTRIBUTING.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (30)
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / Licence consistency
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: governance / Exemption ratchet
  • GitHub Check: governance / Guix packaging policy (Nix retired)
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: governance / Actions lockfile verify
  • GitHub Check: governance / Debt ratchet
  • GitHub Check: governance / Live Actions policy (credentialed advisory)
  • GitHub Check: governance / Allowlist Preflight
  • GitHub Check: governance / Code quality + docs
  • GitHub Check: governance / Security policy checks
  • GitHub Check: governance / Language / package anti-pattern policy
  • GitHub Check: scan / gitleaks
  • GitHub Check: governance / Check Workflow Staleness
  • GitHub Check: scan / shell-secrets
  • GitHub Check: scan / rust-secrets
  • GitHub Check: scan / Hypatia Neurosymbolic Analysis
  • GitHub Check: Groove manifest check
  • GitHub Check: Workflow and session contract validation
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Patch Bridge CVE triage
  • GitHub Check: Validate A2ML manifests
  • GitHub Check: analyze (actions, none)
  • GitHub Check: estate-audit
  • GitHub Check: panic-attack assail
  • GitHub Check: openssf-compliance
🧰 Additional context used
🪛 markdownlint-cli2 (0.23.2)
.github/CONTRIBUTING.md

[warning] 9-9: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


[warning] 12-12: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🔇 Additional comments (3)
.github/CONTRIBUTING.md (3)

6-7: LGTM!

Also applies to: 13-14


24-24: LGTM!


98-101: LGTM!


📝 Summary

Summary by CodeRabbit

  • Documentation
    • Updated the contributing guide with the repository’s concrete details.
    • Corrected clone, toolbox, repository structure, and issue-label references.

Walkthrough

The contributing guide replaces repository placeholders with concrete hyperpolymath/fraying-model-computational-testbed values in commands, the repository tree, and issue-label links.

Changes

Repository documentation

Layer / File(s) Summary
Concrete repository references
.github/CONTRIBUTING.md
Clone and toolbox commands, the repository tree, and issue-label links now use the concrete repository values.

Priority: ⬇️ Low

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

Change: Other

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains some changes, but it omits the required template headings, RSR Quality Checklist, Testing section, and Screenshots section. It also does not describe all changes listed in the… Use the repository template headings. Add the complete RSR Quality Checklist with applicable items marked, record the testing performed, state whether screenshots or terminal output apply, and update the change summary to include all repair…
✅ Passed checks (4 passed)
Check name Status Explanation
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…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title identifies a documentation change to the contributing guide and matches a stated aspect of the change, but it does not describe the broader token and formatting repairs.
Full details: Description check

Explanation

The description explains some changes, but it omits the required template headings, RSR Quality Checklist, Testing section, and Screenshots section. It also does not describe all changes listed in the PR objectives.

Resolution

Use the repository template headings. Add the complete RSR Quality Checklist with applicable items marked, record the testing performed, state whether screenshots or terminal output apply, and update the change summary to include all repairs in the PR objectives.

  • Fix all pre-merge checks with AI

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks the guide with care
Concrete paths now lead somewhere
The tree names match the place
Labels link to the right space
Clean instructions wait there

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

The tree block was hard-wrapped by the AsciiDoc->Markdown conversion, so it
rendered as a paragraph rather than a tree, and it still listed
CONTRIBUTING.md at the repository root, where the guide no longer lives.

Rebuilt from the tree's own content: depth recovered from the `|` continuation
bars that survived the wrap, the guide entry moved under `.github/`, `#`
escapes unescaped, the last entry of each group restored to `└──`, and the
block fenced so it renders as a tree. Every annotation ("Perimeter 1-2") is
preserved - nothing is invented and nothing is dropped.
The repository-structure block listed `CONTRIBUTING.md` at the repository
root, but the guide lives at `.github/CONTRIBUTING.md` - the entry pointed
at a location it had already moved away from. The entry is moved under the
tree's existing `.github/` branch, at the block's own comment column; the
layout of the rest of the tree is untouched.

Placeholder tokens in the block resolve to real values.
@hyperpolymath hyperpolymath changed the title fix(docs): repair the contributing guide content defects fix(docs): list the contributing guide where it actually lives Sep 19, 2026
…ting guide

The guide is instantiated from the estate template, whose own copy legitimately holds
`{{MAIN_BRANCH}}`. Here it was never substituted, so the reader is told to check whether
a bug "is already fixed in `{{MAIN_BRANCH}}`". Resolved to this repository's default
branch. One token, no other change.
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit b917d12 into main Sep 19, 2026
31 of 34 checks passed
@hyperpolymath
hyperpolymath deleted the fix/contributing-guide-content branch September 19, 2026 15:08
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