Archives for the tag: git

Following the git 2.0.0 release two-and-a-half months ago we're being treated to a new minor version of git, 2.1.0, with a host of exciting new features! The full release notes are available here, but they can be a bit terse if you're not deeply involved in the git community. This blog is my own commentary on some aspects of the release that got us excited at Atlassian. Better pager defaults The quotes in this article are lifted directly from the release notes, with my own commentary below. Since

Continue reading »

Today's best software is made not by lone hackers coding in solitary basements, but by teams of "makers" working together to build the next great thing. But without shared workflows, rigorous testing, and proper communication, the path to release day can look more like a Gordian knot. Enter the Git Essentials solution from Atlassian: planning, tracking, source code management, builds, and deploys–all in a single integrated suite. With these powerful tools, teams can coordinate their work

Continue reading »

Nowadays applying a fix to a project is as easy as creating a fork - which conjures up a full remote copy of the project for you to hack on - selecting the file you want to change, pressing Edit and committing your fixes. What if you are at the receiving end of a pull request (abbreviated PR in the following) instead? Using a polished web UI is great and often that's all you need. Click a button to Approve, click a button to Merge and you're done. But that's not always the case! It's a common

Continue reading »

At the heart of every software team is a vibrant culture around creation, organization, and delivery of work. All types of work – be it new features, bugs, spikes… are called 'issues' inside of JIRA. Issues provide a flexible way to organize and distribute work across the team so that everyone remains productive and the whole organization runs at a smooth cadence. This article will focus on three key mistakes teams make and how to correct them when using issues to track work. From feature

Continue reading »

Last week, Tim Pettersen and I held a webinar on optimizing your CI system for Git. We had a great time putting it together, and attendees asked some truly excellent questions, so I think we can safely call this one a success. To sum up, we covered... Why branch-and-merge workflows are so effective (and easier in Git than in SVN, et al) Strategies for reducing build times How to reap the benefits of "pure" CI without piling changes willy-nilly onto a central branch Git hooks that reinforce

Continue reading »

As Git solidifies its position as the version-control-of-choice in the workplace, Stash is delighting those workplace Git users. And it's no surprise: Stash is fantastic for organizing repos, digging into the code, and managing the flow of code from branch to branch. But... If you're not using Bamboo for continuous integration and delivery in combination with Stash, you're not maximizing Stash's full potential. Here's why. Efficient use of time & build resources One thing nearly all

Continue reading »