Skip to content

Commit fc0e881

Browse files
mazimkhanKostyaSha
authored andcommitted
Fixdoc (#251)
* Doc: Warn about merge conflicts when using PR trigger Branch specifier `pull/pr#/merge` silently gives commits up to which PR was mergeable. Any commits after a merge conflict are not present in that branch. * Fix cross reference * Slight reword
1 parent 9e7a9fd commit fc0e881

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

docs/Configuration.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ build for merged state or '/head' for building exact PR commits, or `$GITHUB_PR_
1616
when PR is not mergeable (according to GH state). Set branch specifier to `origin-pull/pull/${GITHUB_PR_NUMBER}/merge`.
1717
This exact link allows to speedup fetch sources.
1818
- Enable "Build GitHub Pull Requests" trigger and configure it.
19+
- Under `Trigger Events` add event `Not mergeable` and check `Skip building unmergeable pull requests?`. As using above branch specifier silently checks out commits up to the point PR was mergeable without complaining. Alternatively, for error indication use <<branch-trigger,Branch Trigger>> and merge using git commands.
1920
- If you want do gatekeepering, then add second repository with i.e. origin.
2021
Add `Merge` extension in from Git SCM and configure post build action for push action.
2122

0 commit comments

Comments
 (0)