forked from assertj/assertj
-
Notifications
You must be signed in to change notification settings - Fork 0
45 lines (42 loc) · 1.69 KB
/
pitest-updated-pr.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
#
# Part two of two stage process for updating PRs with pitest results when accepting PRs from untrusted forks.
#
# The version of this file that runs is the version in the main/master branch, NOT the version in the PR. It must therefore
# be committed to main/master before the process can run for the first time.
#
# This workflow takes an artifact containing pitest results generated in part one, and updated the PR. It runs with
# write access.
#
# See https://blog.pitest.org/oss-pitest-pr/
name: Comment on the pull request
# read-write repo token
# access to secrets
on:
workflow_run:
workflows: ["Receive"]
types:
- completed
jobs:
pitest-update-pr:
if: ${{ github.event.workflow_run.conclusion == 'success' }}
runs-on: ubuntu-latest
steps:
- name: debug
uses: hmarr/debug-action@v2
- name: Setup Java
uses: actions/setup-java@v2
with:
distribution: 'zulu'
java-version: 11
- name: Download artifact
uses: dawidd6/action-download-artifact@v2
with:
workflow: ${{ github.event.workflow_run.workflow_id }}
name: pitest
path: target/pit-reports-ci
workflow_conclusion: success
- name: update pull request
# The updatePR maven goal is used here with an explicit version. This allows us to upload without checking out
# the code, but does mean the version here must be maintained. An alternative would be to checkout the code and use
# the github goal. This will work as long as the artifact is extracted to the maven target directory
run: mvn -DrepoToken=${{ secrets.GITHUB_TOKEN }} com.groupcdg:pitest-github-maven-plugin:0.1.0:updatePR