GitHub vs. GitKraken

GitHub is well suited for software development, GitHub is particularly well suited for software development projects, where teams need to collaborate on code, track changes, and review code changes. Also for open-source projects, GitHub is an ideal platform for open-source projects, where teams of developers from all over the world can collaborate on code and contribute to projects. For documentation, GitHub provides a platform for creating and sharing documentation, making it an ideal solution for teams that need to create and maintain documentation. On small and medium-sized teams GitHub is well suited as those teams that need to collaborate on software projects and track changes to their code.

The software is easy to use and share within our team. Licensing and setup is straightforward. The product just works and we love it.

Incentivized

• As a repository it's great. It houses almost all the open-source applications/code that anyone can fork and play with. A huge collection of sample codes available with problem statements across different domains make Github a one-stop location.
• I use GitHub with Windows and the Git Bash is superb. It [is] a powerful alternative to the Command Prompt and Powershell. Allows me to run shell scripts and UNIX commands inside the terminal [on] a Windows PC.
• GitHub integration with almost all cloud development/deployment platforms is amazing. Deploying a new application in Azure is really smooth. Just link the GitHub repositories and it's good to go. From automatic build to deployment everything is just amazing.

• Customizable workflow steps help organize projects
• Time tracking down to seconds helps to estimate sprints
• Burndown charts let you know when to plan your next release

Incentivized

• When browsing history of a file, GitHub could make it easier to see the file after a particular commit instead of just being able to quickly view the commit. I'd like to be able to see the commit or the file itself in one click.
• I would like to be able to view commits by user.
• I would love to be able to traverse code on GitHub (go to definition, etc) - the good news here is that they are working on these features!

Incentivized

• Timing Out - when editing a story or bug, occasionally Axosoft will time out and all changes will be lost
• Viewing past sprints can be hard to locate
• Multiple users within a Story - Axosoft could do a better job managing multiple users on the same story
• User Interface isn't entirely user friendly and looks a bit outdated

Incentivized

GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.

- Easy to use compared to other version control software. UI interface makes it easy to use, as well as protects against making a major mistake by deleting code, etc. - UI looks modern. - Support for multiple platforms, which I assume will only get better with time. - Student benefits are awesome! - The size limitations on their repositories make sense to me. Not too crazy but realistic from a business perspective.

Incentivized

Once you get the hang of Axosoft, I think it's easy to use however... getting the hang of it takes quite a bit of time. Additionally, once Axosoft makes an update, it can be difficult to find your bearings again. Like I said, once you know how to use the product, I think it's easy but it takes a bit to become comfortable and confident with Axosoft

Incentivized

It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.

Incentivized

At the time to evaluation - Bitbucket was very tightly integrated into Atlassian’s suite of tools. For an organization that is starting out and looking to spend limited funds effectively - the cost/benefit of using that suite of tools usually doesn’t make sense. Granted things may have changed since then (its been over 5 years) - but at the time GitHub was effective - and all prospective engineers knew about it and already had accounts. This made it very easy to add to the organization and not lose time in training, etc. Developers seem to really love GitHub above most other tools out there - so that plays into the decision making as well.

Incentivized

I actually like JIRA better, to me the UI is a lot cleaner. Easier to use, and search tickets.

Incentivized

• Github has increased our rate of code development, increasing our publishing rate. This helps bring attention to the research we are doing and ultimately brings in more funding for further research.
• Because GitHub makes my team more efficient, we are able to put more hours into code development / report writing rather than agonizing over different versions of code created without version control software.
• We use a paid version of GitHub, because we work through private repositories, but the increase in productivity, efficiency, and research progress is definitely worth the price.

Incentivized

• Productivity bump for developers over previous software
• Code is never gone forever and can be found if needed
• Allows us to collaborate and finish projects faster

Incentivized