Skip to content

Commit eb64860

Browse files
committed
use numbered steps in submit more changes section
1 parent 534964d commit eb64860

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,15 @@ Give me a list of ids/maps and I will send you up to date map files for whicheve
33

44
## How to send in your edits using github
55
1. Fork this project using the button on the github page
6-
2. Create a new branch named whatever you like
6+
2. Create a new branch named whatever you like (asdfasdf, borderlands-fix, submission1)
77
3. Edit mapfixes_bhop.txt or mapfixes_surf.txt with your uploaded model ids, commit your changes to your new branch
88
4. Make a Pull Request requesting to merge your branch into the main branch in this repository
99

1010
### I already have a fork, how do I submit more edits
11-
This is where making a new branch comes in handy. You can use the "Sync fork" button on your fork's main branch page to sync the changes since the last time you submitted, and then make a new branch again.
11+
This why you made a new branch the first time.
12+
1. Use the "Sync fork" button on your fork's main branch page to sync the changes so you make your edits on the latest version
13+
2. Go to step 2 (Create a new branch) in the section above
14+
If you didn't make a new branch and have "This branch is 2 commits ahead, 4 commits behind krakow10:main." you will need to fight github to reset your main branch to match the version here so that it's compared to the right version.
1215

1316
### I don't want to do any of this
1417
That's ok, you can just DM me the information and I will add it here.

0 commit comments

Comments
 (0)