#Git add remote fork Patch
#Git add remote fork code

A link to the branch on GitLab, whose text is the branch name (example: 3181657-test-only).Each section contains (some areas will not be present if a merge request has not yet been created on this branch): One or more branch and merge request sections (one per branch that has been created).A link saying Show commands, which will show you commands to clone the issue fork and other useful operations.Either a button where you can Get push access, or text saying You have push access.

The link text is the fork repository name, which is PROJECT-ISSUE_NUMBER where PROJECT is the short/machine name of the project, and ISSUE_NUMBER is the issue number (example: drupal-3181657). A link to the GitLab page for the issue fork.Here is a list of what this area may contain, from top to bottom: If you are on an issue page, and a fork has not yet been created for that issue, you can create an issue fork by clicking the Create issue fork button below the issue summary on the issue page:Īfter one or more branches and merge requests have been made on an issue fork, the Issue fork area below the issue summary on the issue page may look rather complex: It starts out as a copy of the main repository for the project, but it allows all community members to commit and push changes.

#Git add remote fork code

Note: There is a separate page for project maintainers with information about merging: Reviewing and merging merge requests Creating an issue forkĪn issue fork is a temporary repository for working on source code changes for an issue.

When the project maintainer deems the merge request is ready, they merge it into the main repository.

This may result in it being sent back for more changes to be made by community members.

When the merge request is deemed ready by the community, a project maintainer gives it a final review.

This may result in additional commits being made in the fork and added to the merge request.

The merge request is tested via automated testing (if the project maintainer has set up automated testing for patches), and reviewed and tested by community members.

When the changes are ready to be reviewed and tested, a contributor makes a merge request.

One or more contributors commits/pushes changes to the fork.

This makes a new, temporary repository that can be used to work on changes to files in the repository.

A contributor forks the repository for the project on an issue.

As of November 2020, we have a new workflow available, similar to what open-source contributors commonly use on sites like GitHub (see sections below for details, and the Related content section for background information, and make sure you have set up Git before trying any of this):

#Git add remote fork Patch

Previously, the main way to contribute source code changes to a Drupal project repository was via patch files (see other pages in this section for more information on the patch workflow). A video introduction to this workflow can be found at