jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 03:16:52 -05:00
Code Issues Projects Releases Wiki Activity

1. Update frontmatter 2. Add subheadings

Browse Source 
Intro property of front matter has been updated to reflect contents of the article. Subheadings are added to the article to improve the logical structure of article.
This commit is contained in:
Sreekar Guddeti
2021-04-30 11:57:22 +05:30
committed by GitHub
parent 82c7a079f5
commit 2c35bf7e01
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
View File

@@ -1,6 +1,6 @@
--- ---
title: About collaborative development models title: About collaborative development models
intro: The way you use pull requests depends on the type of development model you use in your project. intro: The way you use pull requests depends on the type of development model you use in your project. You can use the fork and pull model or the shared repository model.
redirect_from: redirect_from:
- /articles/types-of-collaborative-development-models/ - /articles/types-of-collaborative-development-models/
- /articles/about-collaborative-development-models - /articles/about-collaborative-development-models
@@ -12,12 +12,9 @@ topics:
- pull requests - pull requests
--- ---
There are two main types of collaborative development models with which you'd use pull requests. ### Fork and pull model
- Fork and pull model In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. You do not need permission to the source repository to push to a user-owned fork. The changes can be pulled into the source repository by the project maintainer. When you open a pull request proposing changes from your user-owned fork to a branch in the source (upstream) repository, you can allow anyone with push access to the upstream repository to make changes to your pull request. This model is popular with open source projects as it reduces the amount of friction for new contributors and allows people to work independently without upfront coordination.
- Shared repository model
In the *fork and pull model*, anyone can fork an existing repository and push changes to their personal fork. You do not need permission to the source repository to push to a user-owned fork. The changes can be pulled into the source repository by the project maintainer. When you open a pull request proposing changes from your user-owned fork to a branch in the source (upstream) repository, you can allow anyone with push access to the upstream repository to make changes to your pull request. This model is popular with open source projects as it reduces the amount of friction for new contributors and allows people to work independently without upfront coordination.
{% tip %} {% tip %}
@@ -25,7 +22,9 @@ In the *fork and pull model*, anyone can fork an existing repository and push ch
{% endtip %} {% endtip %}
In the *shared repository model*, collaborators are granted push access to a single shared repository and topic branches are created when changes need to be made. Pull requests are useful in this model as they initiate code review and general discussion about a set of changes before the changes are merged into the main development branch. This model is more prevalent with small teams and organizations collaborating on private projects. ### Shared repository model
In the shared repository model, collaborators are granted push access to a single shared repository and topic branches are created when changes need to be made. Pull requests are useful in this model as they initiate code review and general discussion about a set of changes before the changes are merged into the main development branch. This model is more prevalent with small teams and organizations collaborating on private projects.
### Further reading ### Further reading