GitHub Action
Comment Pull Request for workflow
A GitHub Action for commenting on pull requests from workflows. Previous comments by the same job are deleted (or hidden or edited), thus avoiding flooding reports of checks based on old commits.
See action.yml for available action inputs.
Note that this action requires pull-requests: write
permission.
Specify comment
input.
- uses: yumemi-inc/comment-pull-request@v1
with:
comment: |
# Test coverage report
...
In this case, previous comments will be deleted.
By specifying previous-comment
input, you can change the handling of previous comments.
Specify one of delete
(default), hide
, edit
, or keep
(do nothing).
- uses: yumemi-inc/comment-pull-request@v1
with:
previous-comment: 'hide'
comment: |
# Test coverage report
...
Comments are grouped by the value of grouping-key
input (default is ${{ github.workflow }}-${{ github.job }}
), and comments in the same group are subject to deletion, etc.
It is often necessary to separate the contents of comments when a check passes and when it fails. You can define it in one step by using comment-if-failure
input.
- run: npm run test
- uses: yumemi-inc/comment-pull-request@v1
if: cancelled() != true
with:
comment: |
:white_check_mark: All tests passed.
comment-if-failure: |
:no_entry_sign: Some tests failed.
See test results from ...
Write the account name after @
.
For example, to mention the creator of a pull request, write as follows:
comment: |
@${{ github.actor }} A critical error has occurred.
The URL for the job log and summary is https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}
.
About job summary: Supercharging GitHub Actions with Job Summaries
To guide this URL with comments, write as follows;
comment: |
Some tests failed.
See details from [here](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}).
It is recommended to write reports such as test results and coverage in the summary rather than in comments.
Basically, this action is used in the pull_request
event trigger, but you can use it in any trigger by specifying pull-request-number
input (default is ${{ github.event.pull_request.number }}
).
Even if this input is omitted, number will be searched for using the commit SHA specified in sha
input (default is ${{ github.sha }}
), but if it cannot be found, explicitly specify pull-request-number
input.