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
5. After making changes to files whilst working, you should add and commit.
73
74
74
75
`$ git add filename.filetype
75
-
$ git commit -m "commit message here"`
76
-
77
-
This saves the current states of your files into the git repo, meaning you can access them exactly as they are now, at any point in the future.
78
-
79
-
6. These are now saved to your branch, but only on your local computer, they now need to be pushed to the remote repo on Github.
76
+
$ git commit -m "commit message here"`
77
+
78
+
This saves the current states of your files into the git repo, meaning you can access them exactly as they are now, at any point in the future.
80
79
81
-
However, before you do these, you want to make sure your branch is up to date with any changes to the master branch.
80
+
6. These are now saved to your branch, but only on your local computer, they now need to be pushed to the remote repo on Github.
81
+
However, before you do these, you want to make sure your branch is up to date with any changes to the master branch.
82
82
83
83
7. So, first checkout to master branch
84
84
@@ -94,9 +94,7 @@ However, before you do these, you want to make sure your branch is up to date wi
94
94
95
95
10. Then you need to *merge* the new master on your local machine with your branch.
96
96
97
-
`$ git merge master`
98
-
99
-
This merges the branch you are one with your local master branch.
97
+
`$ git merge master` This merges the branch you are one with your local master branch.
100
98
101
99
11. You can then push your branch to the remote, save in the knowledge that is up to date with the current remote master, which means when you make a pull request it should merge a lot easier.
0 commit comments