It starts out as a copy of the main repository for the project, but it allows all community members to commit and push changes. 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):
#Hide easy doc merge 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
0 kommentar(er)
