You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps I misunderstood the API of this action, but it seems like there's some assumptions I made that does not align with how this workflow works.
My use case:
I want to create a PR from branch-B to branch-A, where branch-B simply contains commits on top of branch-A
You can think of this as creating a PR from a development branch into production branch
What this means is that I don't intend on making any commits in the Workflow context itself, and simply want to create a PR
but this quickly resulted in empty PRs that ended up not being opened because the Workflow attempts to rebase on top of master and thus does not detect that there are changes between branch and base, when in fact there are changes.
Branch 'release-branch' is not ahead of base 'master' and will not be created
How can I use this Action given my use case above? Is it even possible?
Steps to reproduce
If this issue is describing a possible bug please provide (or link to) your GitHub Actions workflow.
The text was updated successfully, but these errors were encountered:
Subject of the issue
Perhaps I misunderstood the API of this action, but it seems like there's some assumptions I made that does not align with how this workflow works.
My use case:
branch-B
tobranch-A
, wherebranch-B
simply contains commits on top ofbranch-A
You can think of this as creating a PR from a development branch into production branch
What this means is that I don't intend on making any commits in the Workflow context itself, and simply want to create a PR
My configuration for this was along the lines of:
but this quickly resulted in empty PRs that ended up not being opened because the Workflow attempts to rebase on top of master and thus does not detect that there are changes between
branch
andbase
, when in fact there are changes.How can I use this Action given my use case above? Is it even possible?
Steps to reproduce
If this issue is describing a possible bug please provide (or link to) your GitHub Actions workflow.
The text was updated successfully, but these errors were encountered: