due -> do
parent
48d56a736e
commit
566630f0c5
1 changed files with 1 additions and 1 deletions
|
|
@ -68,7 +68,7 @@ If you were to imagine what the below does visually, it sort of looks like this
|
|||
git checkout -b <my new branch>
|
||||
```
|
||||
|
||||
Edit all the things you need to edit - that might be adding new files, changing existing ones, whatever the case may be. The rule of thumb is to try and keep all changes grouped in logical commits; if you need to due 2 things which are not really related, commit the work as 2 unique commits for example with nice comments. There is a bit of an art to this you will learn over time.
|
||||
Edit all the things you need to edit - that might be adding new files, changing existing ones, whatever the case may be. The rule of thumb is to try and keep all changes grouped in logical commits; if you need to do 2 things which are not really related, commit the work as 2 unique commits for example with nice comments. There is a bit of an art to this you will learn over time.
|
||||
|
||||
Commit your local edits to your local working copy:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue