Skip to content

docs: align website contributing guide with root (#1980) - #1996

Merged
igorls merged 1 commit into
MemPalace:developfrom
mvalentsev:docs/1980-contributing-parity
Aug 15, 2026
Merged

docs: align website contributing guide with root (#1980)#1996
igorls merged 1 commit into
MemPalace:developfrom
mvalentsev:docs/1980-contributing-parity

Conversation

@mvalentsev

Copy link
Copy Markdown
Contributor

What does this PR do?

Fixes #1980.

The website copy of the contributing guide (website/reference/contributing.md)
had drifted from the authoritative root CONTRIBUTING.md. Beyond the branch
contradiction in #1980, two more setup steps were out of sync, and all three
push contributors toward the "avoidable triage load" the report describes:

  • PR target (the reported bug): the website said to open a PR against
    main. Contributions merge into develop; main holds tagged production
    releases only (per the ROADMAP.md branch model), so a PR against it gets
    re-targeted or closed.
  • Getting Started cloned MemPalace/mempalace directly, with no fork and
    no upstream remote. That contradicts the "Fork the repo" step further down
    the same page.
  • pre-commit install was absent. That step installs the hook pinning ruff
    to CI's exact version; without it a contributor's code passes local lint and
    then fails CI on push.

Root CONTRIBUTING.md was already correct and is untouched. Only the website
copy changed.

How to test

  • grep -n "PR against" CONTRIBUTING.md website/reference/contributing.md now
    shows develop in both.
  • Single file changed, no new doc links, so the VitePress build is unaffected.

Checklist

  • Docs-only change, no code touched (pytest / ruff check . scope unchanged)
  • No hardcoded paths
  • No new documentation links (VitePress dead-link build unaffected)

The website copy of the contributing guide had drifted from the
authoritative root CONTRIBUTING.md, sending contributors down paths that
create avoidable triage load:

- PR target said `main`; the repo merges PRs into `develop` (`main` is
  tagged releases only). This is the contradiction reported in MemPalace#1980.
- Getting Started cloned the upstream repo directly, with no fork and no
  upstream remote, contradicting the "Fork the repo" step below it.
- The `pre-commit install` step was missing entirely, so the ruff
  version pin CI enforces never got set up locally: code passes local
  lint, then fails CI on push.

Bring the setup steps and PR target into parity with root.

Fixes MemPalace#1980

Co-authored-by: et1975 <623703+et1975@users.noreply.github.com>
@mvalentsev
mvalentsev force-pushed the docs/1980-contributing-parity branch from ca6d955 to d9bae30 Compare August 11, 2026 20:57
@igorls
igorls merged commit f3b759c into MemPalace:develop Aug 15, 2026
9 checks passed
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.

docs: contributing guides contradict each other on PR target branch (develop vs main)

2 participants