Skip to content

Commit 29f5a3d

Browse files
committed
docs: Remove default branch name
1 parent 7a6e4f9 commit 29f5a3d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Docs/Contributing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In most cases, you can get started immediately with making the changes and creat
2222

2323
**Note:** You must fork the Open Rails repository before you start working on it. We do not allow you to push branches to the official repository.
2424

25-
**Note:** You should do your work on separate branches; they must be created from the "master" branch and pull requests must merge back into the "master" branch, unless we direct you otherwise.
25+
**Note:** You should do your work on separate branches; they must be created from the default branch and pull requests must merge back into the default branch, unless we direct you otherwise.
2626

2727
### Documentation and translations
2828

@@ -168,7 +168,7 @@ When we start preparing for a new Stable Version, all code in the Testing Versio
168168

169169
### Submitting your code
170170

171-
When you're done writing code, you should make a pull request on GitHub from your fork's branch back to the official repository's "master" branch. The title and description of the requests should concisely indicate what bug or feature you've implemented and you will need to include links to whichever of the following are appropriate:
171+
When you're done writing code, you should make a pull request on GitHub from your fork's branch back to the official repository's default branch. The title and description of the requests should concisely indicate what bug or feature you've implemented and you will need to include links to whichever of the following are appropriate:
172172

173173
- Bug report
174174
- Road-map card

0 commit comments

Comments
 (0)