Where people build software.
Rated Overall Score
Total Ratings Ratings
We use Github for all our code and development at GoSquared. Github Issues is incredibly versatile as a system for team dev tasks.
Just use GitHub.
easy integration with other apps, secure access, personal account is fairly priced, though business account pricing is expensive with BitBucket being free
We're a very engineering focused company so having everything, even non technical tasks, as Github issues/wiki's gives us one common tool that we all use regularly instead of having different information in different tools. We even se github as an Applicant Tracking System for interview with each candidate being an open issue that moves through milestones.
Works as advertised.
I think it was sensational 5 years back but doesn't really offer any additional value and they have revised the UX multiple times with no real benefit.
Github issues are weak, but we also don't invest a lot of effort into any sort of bug tracking. So this is partly a process/discipline issue on our end.
Great for publicly discussing issues with community. Helps that I have an open source product.
Defacto code repo. Although rushed, we still enforce the "git flow" models with branches and PRs so we're aware of what's going on.
For development tasks, GItHub Issues is the best way to tie tasks to PRs. For us: creating/labeling an issue = backlog; setting a milestone = next; assigning a developer = in progress; closing an issue = done.
It works. Nothing special.
Good integrations. Review feature is pretty good. Permissioning is somewhat limited. E.g. no way to allow assignment of reviewers without granting write access.
The best way to manage your source code.
They're the leaders in the space, so pretty much everyone has used them. I haven't found a compelling reason to evaluate a competitor.
Kind of the standard, not really sure why you'd go anywhere else. Works well and we manage everything through pull requests.
As a founder responsible for our product, design and engineering teams, Github was absolutely essential. Besides core Git-based functionality, we loved how other services easily integrated into our Github accounts and repositories. We used tags to mark releases (and rollback if we encountered any production issues that snuck by our QA and staging environments), robustly used commits, pull requests and general codebase hygiene to map closely to our Agile-ish processes and helped immensely with things like code reviews and pair programming.
Best in class for repository hosting.
Best way to manage your source code
We've been using Github for 4+ years to manage 10+ repos for an engineering team of 10-20 engineers in two different locations. It works. No complaints.
Git add .; Git commit; Git pull --rebase; Git push;
Does everything I need. Only gripe is about permissions. There should be per-repo permissions...
Its the best!
Easy to use. Great features for developers
We are active open-source contributors, both to our own repositories and to others'. GitHub is the place to be.
We use GitHub Issues to keep our bug and feature requests close to where the fix is. You can also cross reference pull requests and issues with simple IDs that resolve into rich links.
Integrated with all our engineering work. We use Projects+Issues to track Design and Engineering work through to shipping.
Best place to host code, and manage code workflows.
Well supported by third party tools. Most developers will have experience with it.
Fast. Easy. Clean. Effective
The hackers that I work with seem to really love it.
Everyone knows how to use it, and overall it works.
Not enough support for various task complexities.
Good community. They've been good to our open source project (Font Awesome), so we feel plenty of loyalty.
Works great. Excellent design. We haven't had any problems.
Free, simple, accessible.
We're open source so it was kind of a no-brainer. We love Gitlab too, but our community is on Github.
our day to day tools to manage project, code and documentation.
Ties all of our bugs with actionable development. We're very product heavy company, so this works great.
It's simple, used correctly it solves everything. Non-devs find it weird, but I've convinced plenty to get a GitHub account and trust all the progress bars.
Simple and effective. Gets brought into Zenhub where we can prioritize and assign from there.
Works well, is already right next to the codebase
Hard to achieve a productive workflow, since we don't use github for code too.
Not only for repository management, but I use the ticketing for tracking tasks. @zenhub is a good addon with this.
Recommend Github for small companies, Jira for bigger ones. We’re moving to Jira now, the transition is important.
Good till a point. We will likely migrate within a year to something more ‘professional.’
Engineering tasks are exclusively tracked on Github Issues.