This limits the workflow greatly. I usually commit a lot of stuff, check things, rebase, amend and then run repoman full (as in: right before the push). Once the ebuild has been committed, repoman does not care anymore about the stable keywords. I already had to fix several commits because of that.
This could probably be done by using git cat-file -e origin/master:app-misc/foo/bar-2.3.0.ebuild to check for the existence on the remote, but I'm not sure how to automagically figure out the remote branch. Maybe just make this work on master branch at least, so we can make a few assumptions.
(In reply to Julian Ospald (hasufell) from comment #1) > I'm not sure how to automagically figure out the remote branch. If you set the upstream using git branch --set-upstream-to, then repoman can use the following command can be used to query it: git rev-parse --abbrev-ref --symbolic-full-name @{u} I found the command here: http://stackoverflow.com/questions/171550/find-out-which-remote-branch-a-local-branch-is-tracking
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.
