[petsc-dev] bitbucket giving wrong information

Jed Brown jed at jedbrown.org
Thu Dec 4 17:25:14 CST 2014

Barry Smith <bsmith at mcs.anl.gov> writes:
>    If we are doing this to generate a local branch that people can work with then we need to be more systemic with no my-branch-name stuff. If follow Dominics approach we should do 
>> git fetch bitbucket:username/petsc their-branch-name:username/pullrequest-their-branch-name
>> git push -u origin username/pullrequest-their-branch-name

Sometimes people don't choose meaningful branch names.  I.e., sometimes
they commit on their master, other times they use different naming
conventions Do_Stuff.  I don't see a problem with the integraor choosing
a better name.  It's useful to annotate the merge (to 'next' and
'master') with "PR #123" so that it gets linked from the PR page.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20141204/07031c5d/attachment.sig>

More information about the petsc-dev mailing list