Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • kdesrc-build kdesrc-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SDK
  • kdesrc-buildkdesrc-build
  • Issues
  • #24

Closed
Open
Created Mar 02, 2019 by Michael Pyne@mpyneDeveloper

Support creating Gitlab fork setup appropriately for a new feature

Similar to #4, but for Gitlab instead of Phabricator.

Would need to use the GitLab Projects API for this, most likely, requiring users to setup a personal API token.

More discussion was provided on the kde-devel mailing list in the Gitlab Evaluation & Migration thread. In particular we'd want this to not just pre-emptively create a new fork every time a repo is cloned but would need to be manually requested.

This would permit users to work on a long-running feature branch and be able to push it back to our Gitlab infra even without being able to immediately push to the authoritative repository itself.

Assignee
Assign to
Time tracking