-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
Create New Branch from the commit #139
Comments
Sorry, I can't quite follow your description here. # At the start of the Workflow, the repo is checked out to the default branch
# by using actions/checkout@v2
git checkout main
# You then immediately create/switch to a new branch
git checkout -b other-branch
# You do a thing to your code which you want to automatically commit
touch foo.txt
# You then run git-auto-commit
stefanzweifel/git-auto-commit-action@v4
# You now expect that the `other-branch`-branch exists on GitHub with
# the changes you made to your code. It would be awesome if you could share more details of your Workflow or what you want to achieve. Meanwhile, have you tried using the
If you provide a |
I think we are on same page. I did try branch option with a new branch name git-auto-commit-action/entrypoint.sh Line 53 in 520c63c
since that branch is not present it cannot do a checkout |
@abhinavkhanna-sf I've created a PR with a possible solution in #140. Could you please test this in your workflows by updating your workflows like this? -- uses: stefanzweifel/git-auto-commit-action@v4
+- uses: stefanzweifel/git-auto-commit-action@feature/create-new-branch-during-checkout If this solves the problem for you, I would tag a new release in the next days. |
Is your feature request related to a problem? Please describe.
Action expects remote branch to be present. It tries to checkout the branch name.
Describe the solution you'd like
While switching to "branch" after fetch, if branch is not found,
Describe alternatives you've considered
None
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: