Re: Don't add tags to ELPA packages -- documentation?

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Phil Sainty <psainty@orcon.net.nz> writes:

> On 2021-08-18 09:51, Eric Abrahamsen wrote:
>> Good to know! I don't suppose you know what happens when we add ELPA or
>> nongnu ELPA as a new remote to a repo already containing tags that will
>> conflict with ELPA tags? Do you know at what stage git will bark at us?
>
> Checking the docs...
>
> Git doesn't push any tags by default, so really git shouldn't bark at
> you unless you've explicitly asked it to do that and there turned out
> to be a conflict.
>
> "git push --follow-tags" will include relevant tags.
> "git push --tag" will include *all* tags.
>
> Unless you're using those, or have configured push.followTags, I think
> you won't have any issues.
>
> The small number of existing tags in the ELPA repository would have been
> pushed in one of those ways.

Okay, this is really useful! Thank you. So it's only an issue if package
maintainers have explicitly pushed their tags to the ELPA repo. So all
the README needs to say, really, is "don't push your tags to the ELPA repo".