pinetime/InfiniTime
1
0
Fork 0
Code Activity
InfiniTime/.github/workflows/pr-comment.yml

57 lines
1.7 KiB
YAML
Raw Normal View History

workflow: Updated workflow comment for all The previous version failed, because it looked for the check from the branch in the fork, but looked for it in the main repo. Now uses the sha to get the commit on which checks were run. Previous description This works by uploading the data from the main workflow with low permissions as an artifact, then downloading the data in a workflow with higher permissions to post the comment. Third party actions are fixed at a commit, in case they get compromised. Also set the build-firmware VM to ubuntu-22.04, which was missed when updating workflow deps earlier.
2023-01-31 08:42:27 +01:00
# THIS WORKFLOW HAS WRITE PERMISSIONS TO THE REPO.
# MAKE SURE IT NEVER RUNS ANY CODE FROM THE FORK
name: PR comment
on:
pull_request_target:
branches: Update files to refer to main instead of develop
2023-03-01 23:42:29 +01:00
branches: [ main ]
workflow: Updated workflow comment for all The previous version failed, because it looked for the check from the branch in the fork, but looked for it in the main repo. Now uses the sha to get the commit on which checks were run. Previous description This works by uploading the data from the main workflow with low permissions as an artifact, then downloading the data in a workflow with higher permissions to post the comment. Third party actions are fixed at a commit, in case they get compromised. Also set the build-firmware VM to ubuntu-22.04, which was missed when updating workflow deps earlier.
2023-01-31 08:42:27 +01:00
paths-ignore:
- 'doc/**'
- '**.md'
jobs:
comment:
runs-on: ubuntu-latest
steps:
- name: Wait for builds to finish
id: wait-for-build
uses: fountainhead/action-wait-for-check@297be350cf8393728ea4d4b39435c7d7ae167c93
with:
checkName: 'Compare build size'
token: ${{ secrets.GITHUB_TOKEN }}
ref: ${{ github.event.pull_request.head.sha }}
- if: steps.wait-for-build.outputs.conclusion != 'success'
pr-comment: Comment instructions instead of failing
2023-03-22 18:10:44 +01:00
run: |
tee comment << EOF
Build checks have not completed. Possible reasons for this are:
1. The checks need to be approved by a maintainer
2. The branch has conflicts
3. The firmware build has failed
EOF
workflow: Updated workflow comment for all The previous version failed, because it looked for the check from the branch in the fork, but looked for it in the main repo. Now uses the sha to get the commit on which checks were run. Previous description This works by uploading the data from the main workflow with low permissions as an artifact, then downloading the data in a workflow with higher permissions to post the comment. Third party actions are fixed at a commit, in case they get compromised. Also set the build-firmware VM to ubuntu-22.04, which was missed when updating workflow deps earlier.
2023-01-31 08:42:27 +01:00
pr-comment: Comment instructions instead of failing
2023-03-22 18:10:44 +01:00
- if: steps.wait-for-build.outputs.conclusion == 'success'
name: Download artifact
workflow: Updated workflow comment for all The previous version failed, because it looked for the check from the branch in the fork, but looked for it in the main repo. Now uses the sha to get the commit on which checks were run. Previous description This works by uploading the data from the main workflow with low permissions as an artifact, then downloading the data in a workflow with higher permissions to post the comment. Third party actions are fixed at a commit, in case they get compromised. Also set the build-firmware VM to ubuntu-22.04, which was missed when updating workflow deps earlier.
2023-01-31 08:42:27 +01:00
uses: dawidd6/action-download-artifact@bd10f381a96414ce2b13a11bfa89902ba7cea07f
with:
workflow: main.yml
workflow: Buildsize comment when simulator fails The workflow checks that the buildsize comparison succeeds. The download artifact step also checks that all of the main workflow succeeds. This isn't necessary, and causes the comment not to be created when the simulator build fails. This change disabled the success conclusion requirement.
2023-01-31 21:21:57 +01:00
workflow_conclusion:
workflow: Updated workflow comment for all The previous version failed, because it looked for the check from the branch in the fork, but looked for it in the main repo. Now uses the sha to get the commit on which checks were run. Previous description This works by uploading the data from the main workflow with low permissions as an artifact, then downloading the data in a workflow with higher permissions to post the comment. Third party actions are fixed at a commit, in case they get compromised. Also set the build-firmware VM to ubuntu-22.04, which was missed when updating workflow deps earlier.
2023-01-31 08:42:27 +01:00
pr: ${{ github.event.pull_request.number }}
name: comment
- name: Find Comment
id: find-comment
uses: peter-evans/find-comment@81e2da3af01c92f83cb927cf3ace0e085617c556
with:
issue-number: ${{ github.event.pull_request.number }}
comment-author: 'github-actions[bot]'
- name: Create or update comment
uses: peter-evans/create-or-update-comment@5adcb0bb0f9fb3f95ef05400558bdb3f329ee808
with:
comment-id: ${{ steps.find-comment.outputs.comment-id }}
issue-number: ${{ github.event.pull_request.number }}
body-file: comment
edit-mode: replace
Copy permalink