-
Notifications
You must be signed in to change notification settings - Fork 2
Git Commands
When starting work on this application we should be cloning it instead of forking it. We are working on a team and we do not need to make a fork for this application unless you are an outside contributor who does not have access to this repository. As the repository is private during the time of this writing, only those who can see it have access. Therefore forking is redundant and serves only to make the git history more messy.
To clone this repository into your working directory: git clone [email protected]:I3uckwheat/cards-of-carousal.git
While working on a feature for this application, it is bad practice to commit your changes directly to main and or develop branches. The avoid this, you must create your own branch. Once you are inside your own branch, you can work on your feature without being impacted by others (and without impacting others with your code).
Create a new branch git checkout -b feature/issue#-feature-name
This will create a new branch and you will be able to start working out of it immediately.
Once you have some code committed, you are going to want to have it pushed to GitHub.
Pushing your branch new to GitHub for the first time: git push -u origin feature/issue#-feature-name
This will push your commits to GitHub, create your branch on GitHub and set your branch as the upstream for you, meaning you will push to that branch on GitHub.
After setting your branch upstream, whenever you need to push, use: git push
git fetch origin <branch name>
git switch <branch name>
This guide is still a work in progress. If there are things you want to add, please bring them up in #help.