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: .github/CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ There are a couple of rules, which are definitely not standard, but highly recom
64
64
65
65
1. If no issue already exists for the work you'll be doing, create one to document the problem(s) being solved and self-assign.
66
66
2. Otherwise please let us know that you are working on the problem. Regular status updates (e.g. "still in progress", "no time anymore", "practically done", "pull request issued") are highly welcome.
67
-
3. Create a new branch—please don't work in the `master` branch directly. It is reserved for releases. We recommend naming the branch to match the issue being addressed (`feature/#777` or `issue-777`).
67
+
3. Create a new branch—please don't work in the `main` branch directly. It is reserved for releases. We recommend naming the branch to match the issue being addressed (`feature/#777` or `issue-777`).
68
68
4. Add failing tests for the change you want to make. Tests are crucial and should be taken from W3C (or other specification).
69
69
5. Fix stuff. Always go from edge case to edge case.
70
70
6. All tests should pass now. Also your new implementation should not break existing tests.
@@ -73,7 +73,7 @@ There are a couple of rules, which are definitely not standard, but highly recom
73
73
74
74
Just to illustrate the git workflow for AngleSharp a little bit more we've added the following graphs.
75
75
76
-
Initially, AngleSharp starts at the `master` branch. This branch should contain the latest stable (or released) version.
76
+
Initially, AngleSharp starts at the `main` branch. This branch should contain the latest stable (or released) version.
77
77
78
78
Here we now created a new branch called `devel`. This is the development branch.
79
79
@@ -101,7 +101,7 @@ git push
101
101
Finally, we may have all the features that are needed to release a new version of AngleSharp. Here we tag the release. For instance for the 1.0 release we use `v1.0`.
0 commit comments