Skip to content

Github actions that merge pull requests with custome ways

License

Notifications You must be signed in to change notification settings

0daryo/github-actions-merger

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

github-actions-merger

github-actions-merger is github actions that merges pull request with commit message including pull request labels.

Usage

  1. Write your workflow file.
  - name: merge
    uses: abema/github-actions-merger@main
    with: 
      "github_token": ${{ secrets.GITHUB_TOKEN }}
      "owner": ${{ github.event.repository.owner.login }}
      "repo": ${{ github.event.repository.name }}
      "pr_number": ${{ github.event.issue.number }}
      "comment": ${{ github.event.comment.body }}
      "mergers": 'na-ga,0daryo'

https://github.com/abema/github-actions-merger/blob/main/.github/workflows/github-actions-merger.yaml

  1. comment /merge on github pull request comment.

  2. pull request is merged, and commit message includes labels.

fix: readme
* documentation
* enhancement

Parameters

You need to set parameters in workflow.

github_token: ${{ secrets.GITHUB_TOKEN }}
owner: ${{ github.event.repository.owner.login }}
repo: ${{ github.event.repository.name }}
pr_number: ${{ github.event.issue.number }}
comment: ${{ github.event.comment.body }}
merge_method: 'merge'
mergers: 'comma separeted github usernames. every user is allowed if not specified'

Note

Setting Branch protection rules is recommended to avoid unexpected merge of pull requests.

About

Github actions that merge pull requests with custome ways

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 94.0%
  • Makefile 3.1%
  • Dockerfile 2.9%