gsd-pr-branch

To exclude planning artifacts from a git pull request diff, you can create a clean branch that filters out commits modifying the `.planning/` directory. This ensures reviewers only see implementation code changes without being distracted by PLAN.md or SUMMARY.md updates.

Your pull request includes `.planning/` directory changes because GSD planning artifacts were committed alongside implementation work on the same branch. Filtering these planning commits generates a separate review-ready branch containing only code diffs.

Yes, you can remove planning commits from a branch without losing code changes by applying deterministic git operations to generate a new branch. This separates GSD artifact history from implementation work, producing a clean PR branch.

The best way to keep code review diffs focused on implementation is to strip GSD planning artifact commits before submitting a PR. Filtering out `.planning/` directory updates ensures the diff contains only meaningful code changes for reviewers.

Yes, this branch filtering targets your main branch by default when creating the clean PR branch. It applies deterministic git operations to exclude `.planning/` commits while preserving implementation changes against the main branch.

You should not use a filtering approach for PR branch management if your repository requires preserving the complete chronological commit history of planning artifacts alongside code changes, as this process strips `.planning/` commits to produce review-focused diffs.