Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
heptapod
heptapod
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 116
    • Issues 116
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

There will be about 1h of downtime on 2020-03-02 at 13:00 UTC+1 (change of servers and upgrade to Heptapod 0.20.0 final)

  • heptapod
  • heptapodheptapod
  • Merge Requests
  • !56

Closed
Opened Jan 30, 2020 by Georges Racinet@gracinet🦑Owner
  • Report abuse
Report abuse

Support for Gitaly opt-ins in Gitlab 10.5

  • Overview 0
  • Commits 7
  • Changes 9

This is an important step towards supporting GitLab versions from 11 onwards, where Gitaly is essentially mandatory.

This is also really useful for development with the GitLab Development Kit (GDK), in which all Gitaly opt-ins are activated by default. In previous experiments with the GDK, we had to hardcode a blanket disabling of all Gitaly features.

Not to be confused with the HGitaly project, what we are doing here is let GitLab go through Gitaly for the inner auxiliary Git repos.

Assignee
Assign to
Reviewer
Request review from
Heptapod 0.12.0
Milestone
Heptapod 0.12.0 (Past due)
Assign milestone
Time tracking
Reference: heptapod/heptapod!56
Source branch: topic/heptapod/gitaly-compat