drupalorg-contribution-helper

To create a merge request on drupal.org, you set up an issue fork, clone the project via git.drupalcode.org, name your branch correctly, push changes, and submit the MR using guided git commands and safety checks.

The correct branch naming convention for drupal.org contributions follows specific patterns based on the issue and project. Using the proper branch naming ensures your merge request is organized and tracks correctly against the issue fork on git.drupalcode.org.

To set up an issue fork for a drupal.org project, you initiate the fork through the drupal.org interface, configure your git remotes to point to git.drupalcode.org, and clone the repository locally to begin applying patches and committing changes.

Yes, you can use standard git commands to apply patches when contributing to drupal.org. The workflow guides you through applying patches correctly within your issue fork before pushing to the remote repository and creating a merge request.

Yes, each drupal.org project requires its own issue fork and remote setup via git.drupalcode.org. The contribution workflow applies across multiple projects, guiding you through remote configuration and MR procedures for each specific collaboration scenario.

Common git pitfalls when submitting a drupal.org merge request include incorrect branch naming, misconfigured remotes for git.drupalcode.org, and improperly applied patches. The workflow includes safety checks to help avoid these frequent contribution errors.