Jira is one of the most popular platforms to plan software development work and to track work. Teams use Jira to create user stories, create and assign tickets, document and track issues and bug fixes, and track the entire development cycle from conception to release. Jira is incredibly useful, but it can also create a lot of email notifications whenever stories or tickets are added, changed, reassigned, or resolved.

If you want to submit good pull requests, start with our contribution checklist. Today, that page talks about what to fork, how to style your code, how to write unit tests and where to push your code. Implicit in all of that is the need to write great code, of course! But this blog post isn’t about writing great code, it’s about making your pull request a great experience for you and your reviewers.

The latest updates to the GitKraken Client are so forking good, you’re sure to break into your Kraken happy dance. We know Keif did. Before we get to the meat and potatoes of what’s new with GitKraken v6.5, here’s the high-level: the GitKraken Git GUI is now 10% faster; with 20% reduced memory consumption; taking up 30% less disk space. How knife is that?!

In this era of globalization, sharing information has been made quiet doable for everyone. Whether it is in the form of text, an image, a video or any other visual form, thanks to the built-in features of mobile devices, like screen recording and screenshots etc, sharing information has become a cinch. In fact, most people prefer sharing information in the form of an image or a video instead of typing lengthy text messages.