Last active
August 29, 2015 14:02
-
-
Save major0/498f83a8606d4b1c5f54 to your computer and use it in GitHub Desktop.
Non-working git config for aiding in a PQM based workflow
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[push] | |
default = current | |
[remote "origin"] | |
url = git@example.com:project.git | |
fetch = +refs/heads/master:refs/remotes/origin/master | |
[remote "pqm"] | |
url = git@example.com:project.git | |
fetch = +refs/heads/personal/user/pqm/*:refs/remotes/personal/user/pqm/* | |
[branch "master"] | |
remote = origin | |
merge = refs/heads/master | |
[branch "personal/user/pqm/master"] | |
remote = . | |
pushremote = pqm | |
merge = res/heads/master | |
rebase = true |
After discussing this issue on irc://irc.freenode.net/git, it seems that this is not possible w/out a branch.<name>.push
configuration directive, which currently does not exist.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempting to configure git so that working w/in a PQM workflow model is considerably easier. In this case we have a personal branch
personal/user/pqm/master
. Whenever we are on this branch we wantgit pull
to rebasemaster
, whilegit push
pushes to the pqm remotepersonal/user/pqm/master
. The act of pushing to the remote branch triggers the PQM software to checkout the revision and run various tests. If all tests pass the PQM makes that revision the new master HEAD.