You can if thats how you wish to proceed. There are no clear-cut rules. Some people like to create a new branch for each new feature. Others like to keep a branch for each user. (Always keep in mind that you can make sub-branches from branches). So try one approach and see if it works out.
If and Brennen1350 have access to your github repository, they can create a branch themselves. You dont have to create it for them. Branches are created from the client (I dont think you can create it from github site)
If you are using the shell, can do this:
git checkout -b thommie_branch
This will create a new branch in his local system. ( it does not exist in remote mahcineā¦github site) He can then make modifications and commit it to this branch. Once he is ready to publsih his changes, he does this:
git push -u <remote_branch> thommie_branch (just put <remote_branch> to origin)
SO:
git push -u origin thommie_branch
The above command will create a new branch named āthommie_branchā on the server and push the code in the local branch āthommie_branchā into it. However if you need a different remote name, you can do taht too
git push -u origin thommie_branch:thommie_remote
āI tend to use the same name for remote and local branches for clarity (althoug this is not always possible).
NOTE: the ā-uā is optional and it will set the upstream for you so that next time you do a pull, it know from where to pull the code.
Now if you want to merge this remote branch into your-own working branch, you do this:
git pull origin thommie_branch
I am not very good at explaining things, so you better take a look at this too: Create a new branch with git and manage branches Ā· Kunena/Kunena-Forum Wiki Ā· GitHub
In Source Tree, creatign a new branch is very simple, there is an option under the branches section.
