Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Automerge changes from release/* to master #17

Closed
jeffchew opened this issue Dec 10, 2019 · 2 comments
Closed

[Question] Automerge changes from release/* to master #17

jeffchew opened this issue Dec 10, 2019 · 2 comments
Labels
question Further information is requested

Comments

@jeffchew
Copy link

I'm new with setting up Github actions. I'd like to set up a flow where any changes to release/* gets merged down to master automatically. Would this configuration work with your action:

name: Gitflow
on: 
  push:
  pull_request_review:
  check_run:
    types: [completed]

jobs:
  build:
    name: Gitflow
    runs-on: ubuntu-16.04
    steps:
    - uses: Logerfo/[email protected]
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}
        release: release/*
        master: master
        label: gitflow
        auto-merge: true
        require-merge: false
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label question to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the question Further information is requested label Dec 10, 2019
@Logerfo
Copy link
Owner

Logerfo commented Dec 11, 2019

Currently, it's not possible to use branch name patterns, only constants. Here's what the branch configurations are used for:

  • dev: only used as a target, pattern would not make sense;
  • master: used as a target (from release) and as head (to dev), pattern would allow more complex configurations for head, but it would break the target;
  • release: only used as head, pattern would allow more complex configurations without breaking anything.

Summing up: patterns will never be supported for the dev branch, they can be supported for the release branch and, if split into two configurations (head and target), master also could support them.
I don't see myself developing this in the near future, but anyone should feel free to send a pull request to achieve this and I'll be glad to release it. This is being tracked by #18.

@Logerfo Logerfo closed this as completed Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants