Personal branches and restrictions with GIT repository

Personal branches and restrictions with GIT repository

[Phil Muldoon]

If you create a personal branch in GDB's GIT repository, that personal
branch has the same restrictions applied to it that Master does. I
understand the caution around Master; we are all still in the learning
phase and the integrity of Master should be maintained with caution.

But in the case of personal branches, do these cautions and
restrictions need to apply? Here's my work-flow to keep my branch up to
date with Master, for myself, and others who follow it.

git checkout master; git pull; git checkout users/pmuldoon/c++compile; git merge master; git push

This just makes my branch = Master + my changes. It does not, of
course, affect Master in any way. However if I try to push the result
of above, I get:

remote: *** Pattern "Merge branch '.*'" has been detected.
remote: *** (in commit 2c03baba0870c1d734c6e35725f1c2a29e35eec7)
remote: ***
remote: *** This usually indicates an unintentional merge commit.
remote: *** If you would really like to push a merge commit, please
remote: *** edit the merge commit's revision history.

As I mentioned above, this is perfectly ordinary and okay with
Master. If that is the policy, well, that's the policy. But do such
restrictions need to apply to personal branches as well?

The hook message hints at a workaround. Rename the commit so it does
not look like a merge. But that seems to be walking into a gray area
to me. Another workaround is to delete the personal branch, recreate
it from Master, and apply your local changes again. While this is not
too bad, it seems "make-work" and not in keeping with GIT's
philosophy.

So this boils down to two questions:

1) Do we need this hook for personal branches?

2) And are users allowed to do whatever they want in their own
   personal branch (within sane defaults)?

Cheers,

Phil

RE: Personal branches and restrictions with GIT repository

[Matthew Fortune]

> git checkout master; git pull; git checkout users/pmuldoon/c++compile;
> git merge master; git push
> 
> This just makes my branch = Master + my changes. It does not, of course,
> affect Master in any way.

If the long term aim is to submit the code to master you may find it
easier to rebase and force push to your personal branch. I'm assuming
force push to a personal branch is allowed.

This keeps all your commits at the top too. This method works well until
you have multiple contributors but with some practice it is possible to
work as a group with rebase+force push.

Matthew

Re: Personal branches and restrictions with GIT repository

[Joel Brobecker]

> So this boils down to two questions:
> 
> 1) Do we need this hook for personal branches?

It's a hook aimed at users who are not very familiar with git
and who might accidently do a merge instead of a rebase.
Un understand that this can be felt as a PITA for more experienced
git users, but it is a really easy mistake to make when one is not
paying attention, and it is also quickly resolved.

> 
> 2) And are users allowed to do whatever they want in their own
>    personal branch (within sane defaults)?

To answer your two questions, I think it boils down to policy
rather than need. The hooks should accomodate the policy.

We can turn all pre-commit checks for user-branches. I don't believe
that the hooks, as currently implemented, support turning off just
that "accidental merge" check. The latter can, of course, be easily
implemented.

FWIW, my take is that if you're going to have your branch hosted
on the sourceware git, it's not a big effort to be following the same
guidelines as other official branches. But if people want it otherwise,
then we can adjust the hooks.

-- 
Joel

Re: Personal branches and restrictions with GIT repository

[Phil Muldoon]

On 28/05/15 14:44, Joel Brobecker wrote:
>
> 2) And are users allowed to do whatever they want in their own
>    personal branch (within sane defaults)?
>
> To answer your two questions, I think it boils down to policy
> rather than need. The hooks should accomodate the policy.
>
> We can turn all pre-commit checks for user-branches. I don't believe
> that the hooks, as currently implemented, support turning off just
> that "accidental merge" check. The latter can, of course, be easily
> implemented.
>
> FWIW, my take is that if you're going to have your branch hosted
> on the sourceware git, it's not a big effort to be following the same
> guidelines as other official branches. But if people want it otherwise,
> then we can adjust the hooks.

Yeah I think this is the question really. And to reiterate not talking
about Master here, just personal branches. Are we free (in the case of
a merge commit to a personal branch), to ignore the hook and commit
anyway? Is it a suggestion or a directive? That's the crux of the
matter.

I've not checked the wiki yet. Maybe some guidelines for personal
branches and/or master branches would be ideal. I'll volunteer to get
one started if nobody else does. Just need to know the said guidelines
first ;)

Cheers


Phil

Re: Personal branches and restrictions with GIT repository

[Joel Brobecker]

> Yeah I think this is the question really. And to reiterate not talking
> about Master here, just personal branches. Are we free (in the case of
> a merge commit to a personal branch), to ignore the hook and commit
> anyway? Is it a suggestion or a directive? That's the crux of the
> matter.
> 
> I've not checked the wiki yet. Maybe some guidelines for personal
> branches and/or master branches would be ideal. I'll volunteer to get
> one started if nobody else does. Just need to know the said guidelines
> first ;)

No one else really provided any opinion so far. Although I would prefer
if personal branches were to follow the standard practices, I do not
have a particularly strong opinion on that. So let's give it another
couple of weeks, and if there are still no opinion, I will let you
chose and document the policy for personal branches.

-- 
Joel