Before we were only using GitHub Issues, but our VP of Engineering is adept at JIRA. He made it work really well for us for creating stories.

We use GitHub for our code repository.

GitHub is our source control tool.

The vast majority of our collaboration is on GitHub--it’s our main source of truth. ZenHub integrates into GitHub and is the project management tool on top of it--and gives GitHub a Trello-like kanban board.

Codetree is like a kanban board on top of GitHub Issues. We use it with a bunch of open source projects. When we manage software tickets, it’s in GitHub Issues.

We use Waffle, layered on top of GitHub, for product and tech projects.

GitHub is for the engineers.

We use GitHub for coding tasks. It is pretty simple and gets things done.

We use GitHub for reporting bugs and issues.

GitHub is good from an engineering standpoint. It’s good for tracking sprints, bugs and adding new features.

We use GitHub dedicatedly, for project management, issue tracking and code management.

Our engineers use GitHub and ZenHub for project management.

We’ve tried Github, Trello, and JIRA, but none of them have been a great fit. They're too technically focused, and forcing business people to use a tool built for developers makes them use the tool less, and less effectively. As a result, we don’t get as good intelligence on the status and needs of our projects. We like Basecamp and will probably end up using it soon, especially as our team grows.

We are currently almost all engineers so any issues that come up are managed through GitHub. I prefer simplicity and fewer tools if possible.

We use Git and GitHub for source control, as the industry standard for a secure & stable place to keep our code.

We’ve spent a lot of time trying out different options. Our company was born out of a research lab, and there we used GitHub to collaborate on projects. GitHub Issues were a common place for discussion and planning. As we grew, that didn’t work for the business side of the company. So we started looking at tools like Trello and Basecamp, but we ended up using a mix of GitHub and Asana. We started using Asana because a co-op student was using it for personal projects and started using it for their projects at ABR. We don’t use Asana very much, just for specific projects. Which project goes into which tool is dependent on whoever is leading the project. We integrate all these things through Slack channels for GitHub and Asana.

Early on when the entire team was just developers, we started out with GitHub Issues. However, GitHub Issues breaks down when you try to use it as a project management tool.

GitHub Issues is fantastic! We hardly ever use Google Drive because we try to keep everything in text format so everything remains searchable, maintainable and migratable. We have a logistics partner that helps with returns and deliveries.

We use GitHub to manage our software development process.

We started off as primarily an Asana shop, but that’s splintered over time. Many teams use GitHub Issues, JIRA, Asana, or Trello heavily. And others use Google Sheets, TeamGantt, and Pivotal Tracker.

We use GitHub for code version control management.

We use GitHub a ton, just like everyone in software. It’s good for what it’s supposed to be.

Our code repository is on GitHub.

We use GitHub for bug tracking.

The engineering team uses GitHub Issues. It is set up to be very specific and tactical. They were already using GitHub for engineering management, so Trello was not as useful for them. When they were using both Trello and GitHub, they were just copying and transferring stuff from GitHub to Trello, which was a waste of time and energy, so now they’re just using GitHub, although more robustly than before.

We use Github to manage our source code. With a distributed engineering team, it makes managing and maintaining our software much easier and organized.

We use GitHub Issues for our internal support ticketing system. When a client has a question or issue, we track it in here.

I really like GitHub Issues a lot. We’ve used JIRA, Pivotal Tracker, etc., and in the end, the engineering team liked GitHub Issues the best. Issues are close to the code, so you get more engaged with them. There isn’t too much shininess on top, and it is pretty simple, but it works really well for us. We also use it for our internal support ticketing system; when a client has a question or issue, we track it in here too. We use it for all project planning, not just engineering.

For engineering, we use GitHub for configuration management and deployment.

The engineers use GitHub for a public repository for our code.

We store code in GitHub.

Everyone loves GitHub.

We do all of our bug tracking, and the development team manages their processes, in GitHub.

We manage our code base in GitHub.

For internal specs, we use GitHub. We have a repository of product specs.

We primarily operate on GitHub.

We use GitHub for our code repositories.

We found that using Asana and Trello to manage projects for our whole company did not work. The tools were too generic to manage everything. For example, we used to use Asana, but it was not integrated into the workflow of the engineers, so nothing was linked to the engineers’ code. We were having to put GitHub links into Asana, and ended up with two sources of truth. We realized that we could just have one source of truth, by moving everything to GitHub. We now do all of our project mapping in GitHub; it’s our code repository, as well as where we put anything related to product. Essentially, GitHub became our Asana. It’s proving to be a really successful solution for us, and we’ve found that we’ve been able to tweak our internal processes with GitHub to replicate what we were doing in Asana.

GitHub is our primary platform for communicating with our developer. We report any issues or enhancements we want to see on the site, and we can easily see what’s being worked on, new issues posted and issues that have been closed. There are a lot of features here that we haven’t even touched, but for what we use it for, GitHub has been great.

We use GitHub a ton. Between that, Slack and Trello, that’s really where we spend the majority of our time.

This is an interesting category for us. We’re basically a bunch of hackers, so we all manage ourselves. We use GitHub, Trello and Slack all together. We use GitHub for version control, and we have GitHub integrated with Slack, so we can all see who is working on what, and all commits to the code base show up in Slack.

We use GitHub for production code versioning.

Our collaboration workflows and accompanying documents are all managed with GitHub.

We use GitHub Issues for source and version control, and for all of our internal workflows. We also use it to keep contracts, invoices and other documents with recent support for binary files. We love GitHub as a whole, and they’re a key partner for our product.

GitHub is where all of our commits, with comments, etc., are built.

We use GitHub to manage our technology stack – developers are committing code directly in GitHub and, therefore, we use the software to manage development sprints. It’s not a great user-interface, but we’ve found it easier than adding yet another tool into the mix.

We use GitHub for anything technical.

GitHub is our repository. Bitbucket has more competitive pricing, but we use GitHub because we like it more.

GitHub is obviously a given for anything for development.

We’re engineers, so we use GitHub to communicate on most things product-related.

We of course use GitHub for product-related documents. For example, we often write drafts of proposals in Markdown and just add them to the relevant repo. (If there isn’t one, we make a new one. We have a lot of GitHub repos.)

We use GitHub Issues and Milestones for project management when it fits more into the flow of our code-- for example when we have a big feature we want to release.

We've toyed with Asana, but I always come back to GitHub. Even our non-technical team members use it to file tasks and issues. Since most of our work loops back to a repository, the integration is obviously better.

We started simply with GitHub issues + Huboard, which worked great for simple needs early on -- But it wasn't quite enough as we grew to a tiny bit more complexity around planning, prioritization, and release tracking.

We chose GitHub for our engineering team because they're already familiar with it. We also use it for general app development.

GitHub is used to for building and compiling software. Our engineers love it.

GitHub is key to everything we do. Given that we’re always working on multiple development projects, GitHub is especially important for us. Their product is awesome. We can use it for issue tracking too. Any project development that we do is connected to GitHub in some way.