-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Committing and pushing a workflow within the runner is not triggering a new workflow on another branch. #32615
Comments
How did you push the branch? You need another token to do that. Action user cannot trigger a new workflow which is by design to avoid recycle triggering. |
After you commented on the user, I made some changes to see if it would solve the problem. Here are the changes I made in the Gitea action
git config --global user.name "myotheruser"
git checkout -b release/1.25.0
git commit -m "Automatic Release Commit"
git remote set-url origin http://myotheruser:[email protected]/myfirstuser/java-spring-template.git
git push --set-upstream origin Even forcing the push with another user, the workflow is not being started on the new branch. |
Can you also post your workflow in the default branch? |
Sure.
|
The "Run Release" task is a composite action that basically executes the script below.
|
|
I created a workflow without composite actions, and the problem persists. I will post the workflow code below.
|
I even managed to do the process via Gitea API using the call to "Modify multiple files in a repository", but it didn't work through commit. |
Description
I have a release process in which the code merged via pull request to the "develop" or "hotfix" branch will perform all the testing and build steps, and if everything goes well, it will create a new branch of the "release/" type with the correct version in some files.
Up to this point, my workflow is working correctly, but when I push the new "release/" branch, it is being created but is not starting the workflow automatically.
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Debian 12
How are you running Gitea?
I'm running Gitea on my Virtual Machine with Debian 12, and the Runners on Docker.
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: