Skip to content

docs: discuss-first for always-on prose; version renumbering at merge - #25

Open
HarshRajSinghania wants to merge 2 commits into
BradleyDB:devfrom
HarshRajSinghania:docs/issue-24-contributing-external-rules
Open

HarshRajSinghania wants to merge 2 commits into
BradleyDB:devfrom
HarshRajSinghania:docs/issue-24-contributing-external-rules

Conversation

@HarshRajSinghania

Copy link
Copy Markdown

What

Documents two contributor rules that were not inferable from CONTRIBUTING.md, as requested in #24:

  • Open an issue first (and link it from the PR) before changing always-on prose: the plan template, the operating-model template, or the managed CLAUDE.md block. Fixes, tests, and generated-file rebuilds are exempt.
  • When bumping the plugin version, use the next number after the dev you branched from and do not rebase only to chase the number; the maintainer renumbers plugin.json and the CHANGELOG entry at merge if dev has moved. The same sentence is on the version checkbox in .github/pull_request_template.md.

Docs-only. No plugin version bump.

Why

#24: review of the first external PR showed both gaps cost review time and are one or two sentences each.

Review notes

  • Diff is CONTRIBUTING.md (Submitting changes) and .github/pull_request_template.md (version checkbox).

  • Wording follows the issue text; existing paragraph about walks that need a tenant was left unchanged.

  • Plugin version bumped in .claude-plugin/plugin.json with a CHANGELOG entry (user-visible plugin change) / not needed (docs-only).

  • Safety boundary: this PR does not touch hooks/gs-admin-guard.mjs or ask-rules generation.

  • Skill edits: not applicable.

  • No test or dev step touched real gs-admin state.

  • No tenant/instance/org-specific data in commit messages or this PR body.

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