To do this, right-click master on the graph and select Create branch here. On our newly created repo, we’ll branch off from master to silo our normal development. Its reference is specifically a moving pointer to an individual commit object. Synonymous with production, typically commits are not made directly to this, but rather are reviewed and merged in.īranches can be thought of as an area to silo where to commit. The newly initialized repository created results in a default master branch. With this example, we’ll take the next step and make a commit to production in a basic workflow. Up until this point, you have created an entire folder representing your project with great potential. Once your repository is initialized and the interface is out of the way, it’s time to get cracking … Whaahh-pssh! … and tie all of the interface and concepts together to perform work on your repository.
#GITKRAKEN GLO UPDATE#
When you change branches, pull in changes, or reset, GitKraken Client will update the files in the working directory to reflect the changes.įor more information on Git repositories, check out the Git repository tutorial blog post including a video from one of our developers. The working directory is the currently checked out version of the files in the local repository. This contains all of the information required for the Git repository and if this folder is deleted, you would no longer be able to switch branches, pull from remotes, or view commit history. When initializing a Git repo or cloning from a remote, you will notice a.
#GITKRAKEN GLO FULL#
It also means if there is a catastrophic event on the remote server, or if another user makes an unwanted change on a remote, all of the other members of the team would still have a copy of the full repo so it can easily be restored.git folder The local repository includes all of the branches, and changes made to the repo, since the time it was created.īecause you make a copy of the entire remote repo, you can change branches, view history, and commit changes without needing a network connection. One of the reasons why Git is so fast when compared to other SCM tools is because all changes are made locally rather than on a remote server. You can easily identify any local branches in the graph as they are shown with the icon.
![gitkraken glo gitkraken glo](https://support.gitkraken.com/img/documentation/glo/github-sync/github-icon.png)
After the branch is created, these branches will be denoted with the Jira icon to reflect its link to a Jira issue.įrom here, it should be possible to configure triggers on the Jira side for changes made to this branch.Ĭlick the icon to copy the issue link or view the item directly in Jira.įor even more goodness between GitKraken and Jira, check out our additional integration features with Git Integration for Jira.Most of the work you do in GitKraken Client is using the local repository, meaning the files and changes are saved on your local machine. The branch name will automatically prefill based on the issue name. You may create a branches tied to an issue from the issue details view.
![gitkraken glo gitkraken glo](https://i.ytimg.com/vi/MoGGGaazuFg/maxresdefault.jpg)
#GITKRAKEN GLO HOW TO#
However for more details about how to write your JQL filters, please refer to the Get started with Advanced Search and JQL guide by Atlassian. Atlassian uses JQL syntax for filters, and the integration will help you auto-complete your filter fields. You may create filters to view the issues you need. Your new issue will automatically sync with your Jira project.
![gitkraken glo gitkraken glo](https://i.ytimg.com/vi/YMCHZLJaark/maxresdefault.jpg)
Hover over any issue to get a preview of the issue Title, Description, Status, Assignee, and Reporter.Ĭlick to select an issue to view the issue details.Īny changes made here will be reflected in your Jira board.įrom the left panel, click the + icon to add a new Jira issue. The app will default to a My Issues filter which will show issues assigned to you.
![gitkraken glo gitkraken glo](https://miro.medium.com/max/1600/1*jxeoY33AWzXmqe3GHzbMEA.gif)
Once connected, your Jira issues will start to appear in the left panel. Hit Accept to proceed.Īlternatively, you may copy the token from the Success page and paste it into the Jira Cloud integration page inside GitKraken Git GUI. You will then be prompted by an Atlassian page to allow GitKraken Git GUI to connect to your Jira account. Set up the integration from the ISSUES pane in the left panel or from Preferences Integrations. To unlock all features for the Jira integration, consider upgrading to a paid GitKraken subscription.
#GITKRAKEN GLO FOR FREE#
The Jira integration is view-only for free users.