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 161
    • Issues 161
    • 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

Mercurial Paris conference scheduled ! Main event : 2022-09-22. Call for papers deadline: 2022-06-17.

  • heptapod
  • heptapodheptapod
  • Issues
  • #669

Closed
Open
Created May 19, 2022 by Georges Racinet@gracinet🦑Owner

Snippets default branch discrepancy

Seen in Docker-based functional tests for Heptapod 0.31.0rc1 and reproduced outside of CI, in Docker context only.

In Heptapod, Snippet repositories should behave exactly as in upstream GitLab. In particular, they are Git repositories.

The problem encountered is that their default GitLab branch (target of the HEAD symbolic reference) is main but the actual branch with content is branch/default. Preferred fix should be not to interfere with GitLab and use whatever it considers the default default branch to be.

Could simply be that we have a hardcoded check on master.

Edited May 19, 2022 by Georges Racinet
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking