Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Lære Create a Pull Request | Making and Reviewing Contributions
Git for Open Source Contributors

bookCreate a Pull Request

When your changes are ready and your branch history is clean, the next step is to submit your work for review through a pull request. A pull request (PR) is a formal request to merge your branch into the main project. In open source, PRs are the standard way to propose changes, allowing maintainers and other contributors to review, discuss, and suggest improvements before your code becomes part of the project. This process ensures code quality and provides an opportunity for learning and collaboration.

12345678910
# 1. Push your branch to your fork on GitHub git push origin my-feature-branch # 2. Open your web browser and go to your fork on GitHub # 3. You will see a "Compare & pull request" button—click it # 4. Fill out the pull request form: # - Provide a clear title # - Write a detailed description of your changes # - Reference any related issues (e.g., "Closes #123") # 5. Submit the pull request to the original repository
copy

Writing a clear pull request description helps reviewers understand your changes and speeds up the review process. Include a summary of what you changed, why you made the change, and any context that might help reviewers. If your PR addresses a specific issue, reference it using the issue number (such as Fixes #42) so it is automatically linked. This makes it easier for maintainers to track progress and ensures your contribution is properly credited.

question mark

What is the main purpose of a pull request in open source collaboration?

Select the correct answer

Var alt klart?

Hvordan kan vi forbedre det?

Tak for dine kommentarer!

Sektion 3. Kapitel 1

Spørg AI

expand

Spørg AI

ChatGPT

Spørg om hvad som helst eller prøv et af de foreslåede spørgsmål for at starte vores chat

Suggested prompts:

Can you explain what happens after I submit a pull request?

What should I include in a good pull request description?

How do I reference an issue in my pull request?

bookCreate a Pull Request

Stryg for at vise menuen

When your changes are ready and your branch history is clean, the next step is to submit your work for review through a pull request. A pull request (PR) is a formal request to merge your branch into the main project. In open source, PRs are the standard way to propose changes, allowing maintainers and other contributors to review, discuss, and suggest improvements before your code becomes part of the project. This process ensures code quality and provides an opportunity for learning and collaboration.

12345678910
# 1. Push your branch to your fork on GitHub git push origin my-feature-branch # 2. Open your web browser and go to your fork on GitHub # 3. You will see a "Compare & pull request" button—click it # 4. Fill out the pull request form: # - Provide a clear title # - Write a detailed description of your changes # - Reference any related issues (e.g., "Closes #123") # 5. Submit the pull request to the original repository
copy

Writing a clear pull request description helps reviewers understand your changes and speeds up the review process. Include a summary of what you changed, why you made the change, and any context that might help reviewers. If your PR addresses a specific issue, reference it using the issue number (such as Fixes #42) so it is automatically linked. This makes it easier for maintainers to track progress and ensures your contribution is properly credited.

question mark

What is the main purpose of a pull request in open source collaboration?

Select the correct answer

Var alt klart?

Hvordan kan vi forbedre det?

Tak for dine kommentarer!

Sektion 3. Kapitel 1
some-alt