PR Comments - GitWhy

How it works

When you push contexts to GitWhy cloud, gitwhy-bot posts a structured comment on any open PR containing the linked commits. Reviewers see:

The prompt that started the work
What was done
Reasoning and key decisions (in a collapsible section)
Files changed and commits
Link to the full context on the dashboard

gitwhy-bot PR comment showing context, story, and metadata

gitwhy-bot posts the full context — title, metadata, story, and reasoning — directly on the pull request.

Post context to a PR

CLI
MCP

# Auto-match all contexts to current branch's PR
git why post-pr

# Post to a PR on a different branch (e.g., from main or a worktree)
git why post-pr --branch feat/auth

# Post specific contexts
git why post-pr ctx_a1b2c3d4 ctx_e5f6g7h8

# Target a specific PR by number
git why post-pr --pr 42

# Preview without posting
git why post-pr --dry-run

When no --pr or --branch is specified, GitWhy auto-detects the PR by scanning open PRs and matching them against branches in your saved contexts.The bot edits its own comment when new contexts are posted — no duplicate comments.See the CLI reference for all flags and output details.

You: "Save this session and post it to the PR."

Agent: [calls gitwhy_save(markdown="<context>...")]
Agent: [calls gitwhy_post_pr()]
GitWhy: Posted context to PR #42

Requirements

Install gitwhy-bot — the GitHub App that posts comments on your PRs.
Activate the repo — sync any context with git why push to activate the repo. This only needs to happen once per repo.

Once both are in place, git why post-pr works for any context in that repo. You can manage active repos at Repositories. The dashboard warns you if the GitHub App is not installed for a repo.

See also

GitHub App setup — install gitwhy-bot
Team Sync — share contexts with your team