We use GitHub for version control.
Co-founder & CEO - Sweet Technology
We use GitHub for our code repository, for issue tracking, and for feature request tracking.
Co-founder - Salesflare
We use GitHub for our code repository.
Co-founder & VP Operations - Woot Math
We use GitHub for product development. It’s great.
Founder & President - RippleMatch
We use GitHub for project management.
Founder & CEO - FoodTrace
We use GitHub for our repositories.
Founder & CEO - Travefy
We use GitHub for source control.
Co-founder & CEO - Frame.io
GitHub Issues is the default issues system within GitHub. It’s a ticketing system with threads that you can comment on.
Founder & CEO - Open Collective
GitHub is nice if you want to build a community around your project. We host open source projects.
Founder & CEO - API Fortress
We are using GitHub for project management and so far it is the tool that works best for us. We have tried all of them, but this is the one that fits our management style.
Co-founder & CEO - StrongDM
We like to contribute to open source projects on GitHub, and contribute with our own libraries and tools that also reside there.
Co-founder & CEO - Adeva
We use GitHub for code development. It works very well.
Founder & CEO - Teleport
We use GitHub to host our code.
Co-founder & COO - Andela
GitHub is great.
Co-founder & CTO - Moving Analytics
We use GitHub for hosted version control on our applications. We also encourage our candidates to store their code here.
VP of Market Expansion - LaunchCode
GitHub is a good way to track issues while we build v2 of our site.
Co-founder and Business Development - Really Good Emails
Our development team uses GitHub for keeping track of their process. They are pretty happy with it.
Co-founder & CEO - Proximi.io
We use GitHub Projects so that we can track everything in the same place. It has the same card based system as Trello and it works for us because it eliminates switching between applications.
Founder & CEO - Yobi
We decided to approach project and product management both in a technical way. We settled for GitHub Issues and GitHub Projects (which is a brand new feature of GitHub), as our team of engineers did not want to have to use yet another tool. We were all already familiar with GitHub.
Co-founder & CEO - Authorea
We tried GitHub Issues but we felt that it was not as good as JIRA.
CEO - Scripted
GitHub is our source control tool.
Co-founder & CTO - Valify
GitHub is for the engineers.
Founder - TouchPoints
We use GitHub for coding tasks. It is pretty simple and gets things done.
Co-founder & CTO - MineWhat
We use GitHub for reporting bugs and issues.
Co-founder & CEO - BottlesTonight
GitHub is good from an engineering standpoint. It’s good for tracking sprints, bugs and adding new features.
Founder & CEO - Do
We use GitHub dedicatedly, for project management, issue tracking and code management.
Co-founder & CEO - Mammoth
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.
Co-founder & CEO - Stylisted
We are currently almost all engineers so any issues that come up are managed through GitHub. I prefer simplicity and fewer tools if possible.
Founder & CEO - iPyxel Creations
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.
Senior Scientist - Applied Brain Research
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.
Co-founder & CEO - Nitrous
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.
Founder & CEO - Coinkite
We use GitHub to manage our software development process.
Co-founder & CEO - Qordoba
We use GitHub for code version control management.
Co-founder - Bauxy
We use GitHub a ton, just like everyone in software. It’s good for what it’s supposed to be.
Co-founder - Bubble
Our code repository is on GitHub.
Co-founder - BuildZoom
We use GitHub for bug tracking.
Co-founder - BuildZoom
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.
Co-founder & CEO - Open Listings
We use Github to manage our source code. With a distributed engineering team, it makes managing and maintaining our software much easier and organized.
COO - Chat Sports
We use GitHub Issues for our internal support ticketing system. When a client has a question or issue, we track it in here.
Co-founder & CTO - URX
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.
Co-founder & CTO - URX
For engineering, we use GitHub for configuration management and deployment.
CEO - OnSIP
The engineers use GitHub for a public repository for our code.
Co-founder & CEO - Blue Bite
We store code in GitHub.
Founder & CEO - Roomi
Everyone loves GitHub.
Co-founder & CEO - Rollout.io
We do all of our bug tracking, and the development team manages their processes, in GitHub.
Founder & CEO - Knowtify
We manage our code base in GitHub.
Founder & CEO - Justworks
For internal specs, we use GitHub. We have a repository of product specs.
Co-founder & CEO - Fieldbook
We primarily operate on GitHub.
Growth and Business Development Strategy - Lob
We use GitHub for our code repositories.
Founder - Qbox
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.
CEO - Zumper
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.
Founder & CEO - Stacklist
We use GitHub a ton. Between that, Slack and Trello, that’s really where we spend the majority of our time.
Co-founder - Underdog.io
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.
Co-founder - Datavore Labs
We use GitHub for production code versioning.
Founder & CEO - messageLOUD
Our collaboration workflows and accompanying documents are all managed with GitHub.
Founder & Head of Operations - Wheelhouse
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.
Founder & Head of Operations - Wheelhouse
GitHub is where all of our commits, with comments, etc., are built.
Co-founder & CIO - Enplug
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.
CEO & Co-founder - Plum Print
We use GitHub for anything technical.
Co-founder - LiveBinders
GitHub is our repository. Bitbucket has more competitive pricing, but we use GitHub because we like it more.
Co-founder - Cloudo
GitHub is obviously a given for anything for development.
Founder - Jurnid
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.
CTO - Bowery
We chose GitHub for our engineering team because they're already familiar with it. We also use it for general app development.
Co-founder & CEO - Ampush
GitHub is used to for building and compiling software. Our engineers love it.
Founder & CEO - Kargo
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.
Founder & President - Lionheart Software
23%Stacklist Startups Are Using GitHub
GitHub is a web-based code repository that’s often used as a project management tool for engineers. It’s a code hosting service, meaning it stores code on the cloud to facilitate collaboration and revision control. It boasts a long list of integrations, issue tracking and its own API to make collaboration as smooth as possible. Github Issues, used by both developers and non-technical folks for workflow organization, enables anyone on your team to submit an issue, assign it as a task, label it for context, and create important milestones and deadlines.
GitHub customers cover the spectrum, from small seed-stage startups to large growth companies. The most popular code repository in the world, GitHub offers an unlimited number of contributors for each repository and has become a fixture of the developer community--at a reasonable price, to boot. It’s a great option for any company that needs to collaborate on code, regardless of size or stage.
GitHub has five pricing plans, all of which offer unlimited members and unlimited public repositories and charges only for private repositories. The free plan includes no private repositories (which means they’re public). The Bronze plan, at $25/month, includes 10 private repositories; Silver, for $50/month, includes 20; Gold includes 50 for $100/month; and Platinum, at $200/month, includes 125. GitHub also charges for data packs that upgrade your storage and bandwidth by 50GB each for $5/month. GitHub also has an enterprise package with additional features and integrations which costs $2,500/year for every 10 developer accounts (as an example, 10 developer accounts would costs $2,500/year, and both 11 and 19 developer accounts would cost $5,000/year.
Visit the website: https://github.com/