uses: mshick/add-pr-comment@v2
Find a file
2020-04-09 08:21:49 -07:00
.github/workflows feat: only provide info logging when comments are not created 2020-04-09 08:21:49 -07:00
dist chore: repackage 2020-04-08 17:19:24 -07:00
docs docs: triggering changes, adding samples 2020-04-08 17:16:12 -07:00
.eslintrc.json initial commit 2019-11-22 17:12:31 -05:00
.gitignore initial commit 2019-11-22 17:12:31 -05:00
action.yml feat: allowing action to run on non PR triggers 2020-04-08 16:39:41 -07:00
index.js feat: only provide info logging when comments are not created 2020-04-09 08:21:49 -07:00
LICENSE initial commit 2019-11-22 17:12:31 -05:00
package-lock.json feat: allowing action to run on non PR triggers 2020-04-08 16:39:41 -07:00
package.json feat: allowing action to run on non PR triggers 2020-04-08 16:39:41 -07:00
README.md docs: update readme with note about use on push triggers 2020-04-08 17:25:34 -07:00

add-pr-comment

A GitHub Action which adds a comment to a Pull Request Issue.

Usage

on:
  pull_request:

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      uses: mshick/add-pr-comment@v1
      with:
        message: |
          **Hello**
          🌏
          !
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        allow-repeats: false

You can even use it on PR Issues that are related to PRs that were merged into master, for example:

on:
  push:
    branches:
      - master

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      uses: mshick/add-pr-comment@v1
      with:
        message: |
          **Hello MASTER**
        repo-token: ${{ secrets.GITHUB_TOKEN }}

Features

  • Fast, runs in the GitHub Actions node.js runtime; no Docker pull needed.
  • Modify issues for PRs merged to master.
  • Multiple posts of the same comment optionally allowable.
  • Supports emoji 😂😂😂!

Use Case

  • Adding a deployed app URL to a PR issue
  • Printing some sort of output to the PR issue for human-readability