Re: Updated tags on repo are not updated when pull

From: PJ Weisberg <pj@irregularexpressions.net>
Date: Apr 3, 2012, 19:44 UTC
Message-ID: <CAJsNXT=mQgt++g-Tz=kfDjC+PC7wJhc77f6zu7vg8GSnJfDq3w@mail.gmail.com>
In-Reply-To: <27353249354D994D8E42D75D75FBA6148967BE@OASBEVEXM01.oaifield.onasgn.com>

On Tue, Apr 3, 2012 at 5:00 AM, Sebastien Tardif <sebastien_tardif@oxfordcorp.com> wrote:

> Like almost everything else, if a local repo is not updated, many things like HEAD and branch may not point to the latest thing.
>
> I agree that using branch is somehow a workaround, but it's still wrong that the tag is not updated by default when doing pull. Even if I find a long documentation about this behavior, it will still be wrong.

The documentation is at least an indication that it was a reasoned decision on the part of the Git developers, so changing it would take more of a discussion than "Please fix."

> Let just admit git is still new, this use case is not original at all, it just show some outstanding issue with Git.

Indeed, I see what you're trying to do with those tags, and I like it.
 There just needs to be a way to implement it while addressing the
concern about tags changing out from under people.  A branch is
*almost* what you want.  Basically it's a branch that no one updates
except the build server under specific circumstances.  You could
enforce that with hooks, but I think the biggest problem is the word
"branch".  People (and UIs) have ideas of what a branch is and what
it's used for, which don't *quite* match the intended use.

I wonder if the Git developers have any ideas on the best way to maintain a pointer to the latest successful automated build, and other such things?

-PJ

Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced.