Important: When creating a branch from an issue please rename the README.mdto avoid conflicts with the main branch.
46fe1b5 (Update GIT-IT.md.)
There are basically three categories of issues;
Feature: May require the creation of a branch, especially if issue title is too broad. e.g.Create visualization site.Major: An issue that affects many parts of theprojectand needs to be fixed ASAP. Could be abug/ tool issue.Minor: There's no need to panic about this issue.
Lets say you want to work on a feature issue for example; JDA-12: Build working visualization site
Create a branch ofjobs-data-analyzer via a JIRA issue panel see image below;
Choose HTTPS, SSH, copy the link and clone the branch;
Clone the branch: git clone -b JDA-12 git@github.com:StackBreakthrough/jobs-data-analyzer.git
cd into the folder and work on your branch
You could also could've simply created the branch from main via your command line ( assuming you initially cloned the main branch );
git checkout -b JDA-12
and switched to it for the following steps. ¯_(ツ)_/¯
Add and commit your changes to your branch JDA-12 in this case.
Then checkout the main branch and merge it with your branch, JDA-12 in this case;
You have a number of options;
git push origin mainorswitchback to your branch (JDA-12) and add more stuff, or push what you already have in that branch to its remote;git switch JDA-12git push origin JDA-12
If this seems like a long process then you might consider just pushing your changes to your remote branch.
Then use Github's pull request to merge it with the main branch.




