Forgejo action to comment pull request
Go to file
2024-06-20 17:55:59 +02:00
.github feat(output): add some action outputs (#297) 2023-10-21 09:16:27 +02:00
act fix: get gitea server URL 2024-06-20 17:55:59 +02:00
src fix: get gitea server URL 2024-06-20 17:55:59 +02:00
.editorconfig fork project 2024-06-20 16:57:36 +02:00
.gitignore fork project 2024-06-20 16:57:36 +02:00
action.yml fork project 2024-06-20 16:57:36 +02:00
eslint.config.js fork project 2024-06-20 16:57:36 +02:00
LICENSE fork project 2024-06-20 16:57:36 +02:00
package.json fork project 2024-06-20 16:57:36 +02:00
pnpm-lock.yaml fork project 2024-06-20 16:57:36 +02:00 fork project 2024-06-20 16:57:36 +02:00
tsconfig.json fix: get gitea server URL 2024-06-20 17:55:59 +02:00

Comment Pull Request - GitHub Actions

What is it ?

A GitHub/Forgejo action that comments with a given message the pull request linked to the pushed branch. You can even put dynamic data thanks to Contexts and expression syntax.

The action is also available as a JS library for integration into other actions.

This project is a fork of by Térence Hollander.


Classic usage

on: pull_request

    runs-on: ubuntu-latest
    name: An example job to comment a PR
      - name: Checkout
        uses: actions/checkout@v3

      - name: Comment PR
          message: |
            Hello world ! :wave:            

Comment a file content

Thanks to the filePath input, a file content can be commented. You can either pass an absolute filePath or a relative one that will be by default retrieved from GITHUB_WORKSPACE. (Note that if both a message and filePath are provided, message will take precedence.)

- name: PR comment with file
    filePath: /path/to/file.txt

Setting reactions

You can also set some reactions on your comments through the reactions input. It takes only valid reactions and adds it to the comment you've just created. (See

- name: PR comment with reactions
    message: |
      Hello world ! :wave:      
    reactions: eyes, rocket

Specifying which pull request to comment on

You can explicitly input which pull request should be commented on by passing the pr_number input. That is particularly useful for manual workflow for instance (workflow_run).

- name: Comment PR
    message: |
      Hello world ! :wave:      
    pr_number: 123 # This will comment on pull request #123

Update a comment

Editing an existing comment is also possible thanks to the comment_tag input.

Thanks to this parameter, it will be possible to identify your comment and then to upsert on it. If the comment is not found at first, it will create a new comment.

That is particularly interesting while committing multiple times in a PR and that you just want to have the last execution report printed. It avoids flooding the PR.

- name: Comment PR with execution number
    message: |
      _(execution **${{ github.run_id }}** / attempt **${{ github.run_attempt }}**)_      
    comment_tag: execution

Note: the input mode can be used to either upsert (by default) or recreate the comment (= delete and create)


Action inputs

Name Description Required Default
GITHUB_TOKEN Token that is used to create comments. Defaults to ${{ github.token }}
message Comment body
filePath Path of the file that should be commented
reactions List of reactions for the comment (comma separated). See
pr_number The number of the pull request where to create the comment current pull-request/issue number (deduced from context)
comment_tag A tag on your comment that will be used to identify a comment in case of replacement
recreate Delete and recreate the comment instead of updating it false
create_if_not_exists Whether a comment should be created even if comment_tag is not found true


Action outputs

You can get some outputs from this actions :

Name Description
id Comment id that was created or updated
body Comment body
html_url URL of the comment created or updated

Example output

- name: Comment PR
  id: hello
    message: |
      Hello world ! :wave:      
- name: Check outputs
  run: |
    echo "id : ${{ }}"
    echo "body : ${{ steps.hello.outputs.body }}"
    echo "html_url : ${{ steps.hello.outputs.html_url }}"    


Depending on the permissions granted to your token, you may lack some rights. To run successfully, this actions needs at least :

permissions:   pull-requests: write

Add this in case you get Resource not accessible by integration error. See jobs.<job_id>.permissions for more information.

Note that, if the PR comes from a fork, it will have only read permission despite the permissions given in the action for the pull_request event. In this case, you may use the pull_request_target event. With this event, permissions can be given without issue (the difference is that it will execute the action from the target branch and not from the origin PR).



The build steps transpiles the src/main.ts to act/index.js which is used in a NodeJS environment. It is handled by vercel/ncc compiler.

$ npm run build