Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • gofoss gofoss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • crixus
  • gofossgofoss
  • Issues
  • #10
Closed
Open
Issue created Oct 01, 2021 by crixus@curlycrixusOwner

Clarify contribution guidelines on how to keep fork up to date with its origin

Checklist

  • This issue is not a duplicate, I've searched the Issue Tracker
  • This issue is not a question, I'm aware that I can submit questions via Mastodon, Twitter, Email, Reddit or Matrix
  • This issue is a content request, and not a bug report, feature request, or anything other

What are you missing or what could be improved?

Guidelines for external contributors to fork, branch & submitting merge request should be reviewed & validated.

What is the solution you'd like to see?

  • Clarify if & how external contributors are to sync the dev branch to their fork?

  • Clarify what happens if external contributors fork the project, clone to their local repository, create an issue branch off of dev, commit to the local issue branch, and meanwhile the upstream dev branch gets modified? Would external contributors have to sync their fork and merge the changes to dev into the local issue branch before opening a Merge Request? Or should this be done by the maintainer? Or is the solution something else altogether?

Do you have additional comments?

See also Issues #8 (closed) and #9

Edited Oct 07, 2021 by crixus
Assignee
Assign to
Time tracking