<commit_before>## jigit

[![Build Status](https://travis-ci.org/Antondomashnev/jigit.svg?branch=master)](https://travis-ci.org/Antondomashnev/jigit)
[![codebeat badge](https://codebeat.co/badges/05115118-11ff-49bb-9b84-73070afb0f3c)](https://codebeat.co/projects/github-com-antondomashnev-jigit)

Keep you JIRA issue statuses in sync with what you're doing actually.

### How it works?

If you're as lazy as me and in the same time working with JIRA for quite a time on a daily basis,
`jigit` may save you some time and make the process a bit better :wink
Let's say you've just cloned a project and
have 2 JIRA issues in `TO DO` in our list: `CNI-1798`, `CNI-1799`.

* You're on `master` branch or whatever you have as a default after cloning;
* You're going to work on `CNI-1798` first;
* `git checkout -b CNI-1798`;
* `jigit` will change the status of `CNI-1798` on JIRA to `In Progress`
  or whatever you set up as a `work in progress` status 🎉;
* Suddenly you have to switch to the higher priority `CNI-1799`;
* `git checkout -b CNI-1799`;
* `jigit` will ask you for a new status for `CNI-1798`, which I suppose a kind of `To Do`,
  and update status of `CNI-1799`;

And you can jump between branches as much as you want, but you will never ever have the wrong status for you JIRA issue :rocket.
You are 😀, a project manager is 😀 - the world becomes a bit better 🙌
<commit_msg>Add gem badge<commit_after>## jigit

[![Build Status](https://travis-ci.org/Antondomashnev/jigit.svg?branch=master)](https://travis-ci.org/Antondomashnev/jigit)
[![codebeat badge](https://codebeat.co/badges/05115118-11ff-49bb-9b84-73070afb0f3c)](https://codebeat.co/projects/github-com-antondomashnev-jigit)
[![Gem Version](https://badge.fury.io/rb/jigit.svg)](https://badge.fury.io/rb/jigit)

Keep you JIRA issue statuses in sync with what you're doing actually.

### How it works?

If you're as lazy as me and in the same time working with JIRA for quite a time on a daily basis,
`jigit` may save you some time and make the process a bit better :wink
Let's say you've just cloned a project and
have 2 JIRA issues in `TO DO` in our list: `CNI-1798`, `CNI-1799`.

* You're on `master` branch or whatever you have as a default after cloning;
* You're going to work on `CNI-1798` first;
* `git checkout -b CNI-1798`;
* `jigit` will change the status of `CNI-1798` on JIRA to `In Progress`
  or whatever you set up as a `work in progress` status 🎉;
* Suddenly you have to switch to the higher priority `CNI-1799`;
* `git checkout -b CNI-1799`;
* `jigit` will ask you for a new status for `CNI-1798`, which I suppose a kind of `To Do`,
  and update status of `CNI-1799`;

And you can jump between branches as much as you want, but you will never ever have the wrong status for you JIRA issue :rocket.
You are 😀, a project manager is 😀 - the world becomes a bit better 🙌

{'fraction_non_alphanumeric': 0.1102915349490692, 'fraction_numerical': 0.0414471373375483, 'mean_word_length': 4.178181818181818, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4498545', 'n_tokens_mistral': 1084, 'n_tokens_neox': 1003, 'n_words': 408}