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
Branch custom actions for Gerrit #301
Comments
I think you can create a custom action for that. You can find some info there: fork-dev/Tracker#123 |
Is it possible to add a variable $branch in Commit Custom Action? That way my action can be $git push origin HEAD:refs/for/$branch, instead of creating a custom action per branch. |
We probably need a new type of custom action - Reference custom action, which could be applied to local and (or) remote branches and (or) tags. Then this action will appear in every branch context menu (either on sidebar on in the commit list). What do you think? |
Not sure about the terminology (maybe Branch custom action can do the trick) but yes what I'm trying to do is pushing a branch, not just a commit. Having the action appearing in the side bar or commit list is good. |
Yes, I agree. Branch custom action should be clearer. (In git both branches and tags are references) OK, I'm adding this to my todo list. I will report ETA later. |
I just released 1.34 with the support of branch custom actions. I'm looking forward to hear your feedback. |
Hi Dan, sorry for the delay. I've just tested it and it's perfectly working. UI is great too. Thanks a lot! |
This is a very specific workflow when using Gerrit Code Review. The commit can't be pushed directly to the origin branch (let's say origin/master) but to a staging branch (origin/refs/for/master) where the commit is validated through the interface and then merged in origin master.
Now in my git config for my repo I have the following:
But Fork doesn't seem to be taken this modification into account. When pushing the only option available is origin/master
Now I'm no git expert so I'm not sure the origin branch should be origin/refs/for/master. I can provide you some logs from SourceTree (I'm trying to switch) if that's helping you.
The text was updated successfully, but these errors were encountered: