... | @@ -16,8 +16,8 @@ The proper procedure to editing code for the first time is: |
... | @@ -16,8 +16,8 @@ The proper procedure to editing code for the first time is: |
|
3. `git checkout -b some_new_branch_name` (might take a few seconds, it makes a branch and switches to it)
|
|
3. `git checkout -b some_new_branch_name` (might take a few seconds, it makes a branch and switches to it)
|
|
4. `git push --set-upstream origin some_new_branch_name` (... just do it. Also: _google it_)
|
|
4. `git push --set-upstream origin some_new_branch_name` (... just do it. Also: _google it_)
|
|
5. edit the code.
|
|
5. edit the code.
|
|
6. before editing more than a few lines, save your progress by:
|
|
6. before editing more than a few lines, save your progress by: `git commit -am "commit message"`.
|
|
`git commit -am "commit message"` . keep the part between double quotes brief, use [this convention](https://github.com/joelparkerhenderson/git_commit_message) and you'll thank yourself later in life.
|
|
keep the part between double quotes _descriptive and short_, use [this convention](https://github.com/joelparkerhenderson/git_commit_message) and you'll thank yourself later in life.
|
|
|
|
|
|
6. hit F8 if Blender is running, to test the changes.
|
|
6. hit F8 if Blender is running, to test the changes.
|
|
|
|
|
... | | ... | |