You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,18 @@ The process for reporting bugs and requesting smaller features is also outlined
38
38
39
39
Pull Requests (PRs) should follow these guidelines as much as possible:
40
40
41
+
### Creating a pull request from a fork
42
+
Below is a general workflow to create a PR from a forked repository. By following these steps, we can avoid granting write permissions to the main repository.
43
+
-[Fork the repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
44
+
- Clone the forked repository
45
+
-[Configuring a remote repository for a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)
46
+
- Sync the forked repository with the main repository
47
+
-[Syncing a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)
48
+
- Create a new branch for your changes
49
+
- Make your changes
50
+
- Push the branch to your fork
51
+
-[Create a PR from your branch to the main repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
0 commit comments