Skip to content

docs: merge policy for conflict resolution - #1209

Merged
Samuel1-ona merged 1 commit into
Samuel1-ona:mainfrom
autarch-agent:docs-1146-merge-policy
Aug 27, 2026
Merged

docs: merge policy for conflict resolution#1209
Samuel1-ona merged 1 commit into
Samuel1-ona:mainfrom
autarch-agent:docs-1146-merge-policy

Conversation

@autarch-agent

Copy link
Copy Markdown
Contributor

What

Adds the explicit merge policy to CONTRIBUTING.md that #1146 asks for: how to resolve conflicts correctly and verify afterwards.

Why

The recurring damage pattern is conflict resolutions that keep both sides of a hunk — 31 files were affected. Duplicate routes/components sometimes compile but break at runtime far from the cause.

Contents

  • Explicit rule: never keep both sides of a conflicting code block
  • Post-resolution verification: duplicate route/export grep checks + pnpm build
  • Requires rebasing on main (with --force-with-lease) before requesting review
  • Full local check (pnpm lint && pnpm test && pnpm build) after rebasing

Resolves #1146

Implements Samuel1-ona#1146:
- explicit rule: never keep both sides of a conflicting hunk (31 files
  were damaged this way per the issue)
- post-resolution verification commands (duplicate route/export checks,
  pnpm build)
- requires rebasing on main + full local check before requesting review
- documents the local parse/build verification step
@Samuel1-ona
Samuel1-ona merged commit 2c7e9a5 into Samuel1-ona:main Aug 27, 2026
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] Document the merge policy that prevents duplicate-block damage

2 participants