Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 163
    • Issues 163
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Issues
  • #432

Closed
Open
Created Mar 02, 2021 by Georges Racinet@gracinet🦑Owner

Pruned tag is still in the way

Heptapod has a protection against tags pointing to obsolete changesets.

It is implemented in py-heptapod, leading to such messages as "Refusing these changes, as they would make tag(s) [xyz] point to the obsolete changeset hhhhhhhhh".

But in the course of checking that, it will see tags that are themselves obsolete (introduced by an obsolete changeset). As a result, a push that obsoletes some changesets can be refused because of a tag that users don't see (perhaps even with the --hidden option because they never pulled it before it got obsolete).

That happened to me yesterday for the preparation of Heptapod 0.20.0 when I was trying to clean up after a misbehaviour in a packaging script. The only workaround is to supersede the obsolete tag first (with hg tag -f) so that it does not point to the changeset to be obsoleted any more.

Desired behaviour:

The check should only guard against non-obsolete tags pointing to obsolete changesets.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking