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: docs/development/Development.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@ The main flow for a contributing is as follows:
101
101
1. Login to github, go to the INAV repository and press `fork`.
102
102
2. Then using the command line/terminal on your computer: `git clone <url to YOUR fork>`
103
103
3.`cd inav`
104
-
4.`git checkout master`
104
+
4.`git checkout maintenance-10.x`
105
105
5.`git checkout -b my-new-code`
106
106
6. Make changes
107
107
7.`git add <files that have changed>`
@@ -114,13 +114,13 @@ The primary thing to remember is that separate pull requests should be created f
114
114
115
115
**Important:** Most contributions should target a maintenance branch, not `master`. See the branching section below for guidance on choosing the correct target branch.
116
116
117
-
Later, you can get the changes from the INAV repo into your `master` branch by adding INAV as a git remote and merging from it as follows:
117
+
Later, you can get the changes from the INAV repo into your version branch by adding INAV as a git remote and merging from it as follows:
0 commit comments