Bug 559632 – repoman commit should have an option for trying to directly push to master if all went well

• Status: RESOLVED WONTFIX
• Product: Portage Development

[Description Pacho Ramos 2015-09-05 07:24:26 UTC]

Previously with CVS we simply needed to run "repoman commit -m "..." ". Now with git we need to, after getting repoman commit running ok, remember to manually run "git push --signed origin master"

Would be possible to have an option for running it directly if repoman commit runs ok (and, then, it shouldn't cause problems to push to master just after that)?

Thanks a lot

[Comment 1 Zac Medico 2015-09-05 13:18:31 UTC]

Also, would be nice to have an option for it to retry the push in a loop, doing fetch/rebase/sign as needed until the push succeeds.

[Comment 2 Agostino Sarubbo 2015-09-05 19:10:07 UTC]

would be also nice have something like --nopush so who want to do one push after some commits, can do it.

[Comment 3 Pacho Ramos 2015-10-18 13:46:11 UTC]

(In reply to Agostino Sarubbo from comment #2)
> would be also nice have something like --nopush so who want to do one push
> after some commits, can do it.

Maybe other option would be to have a "repoman push" that would run git push as expected (git push --signed origin master) keeping repoman commit only for committing :)

[Comment 4 Martha G Smons 2020-12-17 11:58:41 UTC]

# 559632 https://goo.gl/2DqXGj

would be also nice have something like --nopush so who want to do one push after some commits, can do it.

[Comment 5 Sam James 2022-07-12 03:18:15 UTC]

repoman support has been removed per bug 835013.

Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.