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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ create a new one that you would like work on and discuss your ideas and use case
30
30
It is always best to discuss your plans beforehand, to ensure that your contribution is in line with our goals.
31
31
32
32
- Fork the repository on GitHub
33
-
- Create a topic branch from where you want to base your work. This is usually master.
33
+
- Create a topic branch from where you want to base your work. This is usually `main`.
34
34
- Open a new pull request, label it `work in progress` and outline what you will be contributing
35
35
- Make commits of logical units.
36
36
- Make sure you sign-off on your commits `git commit -s -m "adding X to change Y"`
@@ -62,7 +62,7 @@ $ cd tracelib
62
62
$ npm install
63
63
```
64
64
65
-
You can find a fixture tracelog to test API changes in the [test directory](https://github.com/saucelabs/tracelib/blob/master/tests/__fixtures__/jankTraceLog.json).
65
+
You can find a fixture tracelog to test API changes in the [test directory](https://github.com/saucelabs/tracelib/blob/main/tests/__fixtures__/jankTraceLog.json).
0 commit comments