-
This can be addressed in 13.0.0:
- Create a special user with permission to manage the project, and then generate an access token for the user
- Create a job secret for the access token in the project
- Configure the pull repository step to use the job secret for property
access token for target project - Configure the branch update trigger to exclude this special user by specifying applicable users as
any except user(<user name>)
-
Previous Value Current Value Open
Closed
-
Thank you very much!
I already had a special user, I simply had to add the exception to the branch trigger:
anyone except user(admin)
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
This is the current workflow:
Unfortunately in the second case OneDev still pushes to GitHub afterwards. This results in loss of commits when a user on GitHub makes more than one in a row.
Is there a way to set it up so that the "Push to remote" job is not triggered if the branch was last updated by the "Pull from remote" one?