Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • py-heptapod py-heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • py-heptapodpy-heptapod
  • Merge requests
  • !28

Merged
Created Jun 28, 2020 by Georges Racinet@gracinet🦑Owner

Protection for subrepos related problems

  • Overview 3
  • Commits 4
  • Pipelines 6
  • Changes 5

See explanations in heptapod#311.

In changesets after the fix for heptapod#310 (closed), what we're doing here is to prevent potential harm by sabotaging server-side subrepos operations.

Of course we should do better in the long run, but that will have to be after %Heptapod 0.14.0

I'm willing to complement with a FAQ entry about subrepos and link that to foss.heptapod.net#62 (closed) to tell users what they can (and can't) do with their umbrella repos on Heptapod for now.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: topic/default/subrepos