gsd-pr-branch

To remove planning files from a git branch before a pull request, rewrite the branch history to exclude commits that only modify .planning/ artifacts, producing a clean PR branch that shows reviewers only relevant code changes.

Filtering out .planning/ commits works by rewriting branch history to exclude commits that only modify planning artifacts like PLAN.md, SUMMARY.md, and STATE.md, while preserving and keeping all code-related changes intact.

You need local git access and the ability to safely rewrite branch history using a tool like git-filter-repo or an equivalent utility, along with permission to force-push the rewritten branch to your remote repository.

The best way to hide GSD planning artifacts from code review diffs is to generate a dedicated PR-ready branch derived from your working branch, filtering out any commits that solely modify files under the .planning/ directory.

Yes, rewriting git branch history to remove planning files preserves code changes by targeting and excluding only those commits that exclusively modify files within the .planning/ directory, ensuring all actual code modifications remain in the final diff.

You should avoid rewriting branch history to clean a pull request if your local environment lacks safe git history rewrite capabilities or if you lack the necessary permissions to force-push the rewritten branch to the remote repository.