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
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 157
    • Issues 157
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • 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
  • #146

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

Some permission user feedbacks get lost

In standard GitLab, push denies come with an explicit reason, which range from not very interesting "You are not allowed to upload code for this project" to actually useful "The repository is temporarily read-only".

The way permission checks work currently in Heptapod, except for the general access/visibility check, GitLab has no idea what the user is trying to do, and can only pass over a permission level to be used by Mercurial.

Hence these user feedbacks are lost. This isn't a big concern for the time being, and there's not so much we can do about it short time, but it's perhaps something we can improve within the hgitaly project.

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