This action will automatically merge your master
branch into dev
and release
into master
through the creation of pull requests that will be automatically merged, if possible and enabled.
Those pull requests will be identified by a label named gitflow
as default.
Create a file named .github/workflows/gitflow.yml
.
name: Gitflow
on:
# To create pull requests.
push:
# To merge pull requests if not possible during the push run. Remove if `auto-merge` is `false`.
pull_request_review:
check_run:
types: [completed]
jobs:
build:
name: Gitflow
runs-on: ubuntu-16.04
steps:
- uses: caseware/gitflow-action@0.0.4
with:
github-token: ${{ secrets.GITHUB_TOKEN }} # The `GITHUB_TOKEN` secret.
name: Gitflow
on:
# To create pull requests.
- push
jobs:
build:
name: Gitflow
runs-on: ubuntu-16.04
steps:
- uses: caseware/gitflow-action@0.0.4
with:
github-token: ${{ secrets.GITHUB_TOKEN }} # The `GITHUB_TOKEN` secret.
auto-merge: false # If `true`, will try to automatically merge the pull requests.
All values are default.
name: Gitflow
on:
# To create pull requests.
push:
# To merge pull requests if not possible during the push run. Remove if `auto-merge` is `false`.
pull_request_review:
check_run:
types: [completed]
jobs:
build:
name: Gitflow
runs-on: ubuntu-16.04
steps:
- uses: caseware/gitflow-action@0.0.4
with:
github-token: ${{ secrets.GITHUB_TOKEN }} # The `GITHUB_TOKEN` secret.
release: release # The `release` branch.
dev: dev # The `dev` branch.
master: master # The `master` branch.
master-target: dev # the target branch of pull requests from the `master` branch
release-target: master # the target branch of pull requests from the `release` branch
label: gitflow # The pull request label.
auto-merge: true # If `true`, will try to automatically merge pull requests. Can also be set to `pull_request_review`, `check_run`, `push`, or a comma-separated combination of these values to only merge when handling the named events.
require-merge: false # If an attempted merge fails, the action is considered to have failed.
You can use (at your own risk) the release
branch instead of the specific version tag.
Never user master
, since the distribution file does not exist in this branch and the action will always fail.
Click here.
If you have suggestions for how close-label could be improved, or want to report a bug, open an issue! We'd love all and any contributions.
For more, check out the Contributing Guide.
BTC: 1LoGErFoNzE1gCA5fzk6A82nV6iJdKssSZ