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
+3-3
Original file line number
Diff line number
Diff line change
@@ -23,18 +23,18 @@ reported the issue. Please try to include as much information as you can. Detail
23
23
## Contributing via Pull Requests
24
24
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
25
25
26
-
1. You are working against the latest source on the *staging* branch.
26
+
1. You are working against the latest source on the *master* branch.
27
27
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
28
28
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
29
29
30
30
To send us a pull request, please:
31
31
32
32
1. Fork the repository.
33
-
2. Working off the latest version of the *staging* branch, modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
33
+
2. Working off the latest version of the *master* branch, modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
34
34
3. Ensure local tests pass.
35
35
4. Run `standard --fix` on your new code to ensure style consistency. Remember to only reformat files relevant to your changes.
36
36
5. Commit to your fork using clear commit messages.
37
-
6. Send us a pull request merging into the *staging* branch, answering any default questions in the pull request interface.
37
+
6. Send us a pull request merging into the *master* branch, answering any default questions in the pull request interface.
38
38
7. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
39
39
40
40
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
0 commit comments