Skip to content

Document which commit a GitHub check is published against #333 - #539

Open
AzazelSensei wants to merge 1 commit into
jenkinsci:masterfrom
AzazelSensei:docs-333-pr-head-vs-merge
Open

Document which commit a GitHub check is published against #333#539
AzazelSensei wants to merge 1 commit into
jenkinsci:masterfrom
AzazelSensei:docs-333-pr-head-vs-merge

Conversation

@AzazelSensei

Copy link
Copy Markdown

Fixes #333

README now explains which SHA this plugin publishes a check against.

GitHub Branch Source already uses the pull request head, even when the job builds the merge into the target branch. Git SCM uses GIT_COMMIT, so origin/pull/N/merge posts the check on GitHub's merge commit instead of the PR head. There is no SHA override in this plugin; use origin/pull/N/head or GitHub Branch Source if the check needs to show on the PR.

Git SCM jobs that check out refs/pull/*/merge publish the check on
GitHub's merge commit, not the PR head. GitHub Branch Source already
uses the pull head SHA.

Fixes jenkinsci#333

Signed-off-by: Abdullah <89297042+AzazelSensei@users.noreply.github.com>
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.

Updating status checks on merge of PR instead of head

1 participant