GitHub is Everything You Need for Version Control
Overall Satisfaction with GitHub
The development department uses private GitHub organizations for version control of web applications and internal analytics programs. Only development uses it, the other departments do not create new code or interact with it so it's only been appropriate for us.
Pros
- Code difference comparison
- Private repositories that are stored outside the organization
- Code highlighting for ObjectScript
- Issues tracking is easy to attach to commit history
Cons
- Syntax highlighting for more obscure file types, like csp (Cache Server Page)
- Better handling or notification of deleted forked repos. If you delete the repo, the pull request will show up as "unknown repository" which creates odd dead ends
- Increases ROI in the long run, because version control, in general, saves time on projects.
- Makes unit testing easier, which is another long run time saver.
They're not listed here, but we've used Deltanji as well which is more suited for Intersystems specific products. But GitHub is far more modernized and can handle anything, and code reviews are a breeze with built-in comparison tools.
Do you think GitHub delivers good value for the price?
Yes
Are you happy with GitHub's feature set?
Yes
Did GitHub live up to sales and marketing promises?
Yes
Did implementation of GitHub go as expected?
Yes
Would you buy GitHub again?
Yes
Comments
Please log in to join the conversation