Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 164
    • Issues 164
    • 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
  • #143

Closed
Open
Created Dec 10, 2019 by Georges Racinet@gracinet🦑Owner

Bookmarks protection is too harsh

If the server side repo has existing bookmarks, but isn't configured to work with bookmarks, and if a user has new values for these bookmarks in the local repo, a push not even mentioning bookmarks gets rejected.

This has been experimented by @timeless developer on hg-git today.

The reason is that bookmark moves are implicitely pushed.

Heptapod should not refuse the push in that case, and just output a message saying that the server-side bookmark hasn't been updated. The refusal should be for bookmarks creations only.

Oh, and by the way, the bookmarks rejection message should mention which bookmark this is about. That would help.

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