Workflow(from master branch @ HEAD):
git branch spam
git checkout spam
vi eggs
git add eggs
git commit <- edit/save commit message
git push --set-upstream origin spam
rbt post -s --guess-summary --guess-description --branch spam
--tracking-branch origin/master -d -p $commit_id"
Now, if I go look at my commit at this point there is no stamp in the
description. The minimum action that I have found to properly stamp the
commit(s) from this point is the following:
$ git pull --no-edit; git push
The problem with this approach is that now extra commits are visible in
Bitbucket.
Where am I going wrong? Is there some step I missed or some set of
directives I can issue through rbt to get the stamp in place without using
git push?
RB 2.5.7
RBTools 0.7.6
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
