Item: GitHub
Rating: 10
Author: Verified User

Overall Satisfaction with GitHub

Use Cases and Deployment Scope

We use GitHub for the code repository. For all the version tracking, collaborating with multiple developer. We also use GitHub co piolet for development. Different version tracking is really helpful when it comes to the back tracking, also bug fixing. We can see where it is changed, who changed, based on the commit message we can say why it was done. Copilot gives a whole new area to play with. so much possibilities.

Pros and Cons

Pros

Collaboration with multiple developers. This is very good. either we can work on same branch, or we can work on different branches, then merge to the one main branch, so that all the codes are available.
Cherry picking is very nice, you want only one commit moved to a different branch? you don't have to merge it with complete branch, just one commit you can move.
Labelling is a wonderful feature, it helps to identify which branch is critical, what to touch, what shouldn't be touched.

Cons

Copilot plugin in visual studio seems to have some issues, it goes offline sometimes, this need to be improved.
Code review can be improved, merging on the page it self not that feasible, we have to resolve it offline then push it sometimes. Auto merge sometimes loses changes if complex.
CI/CD configuration is kind of messy, it is hard to maintain if we have to make continues changes to the file.

Return on Investment

As a developer it only helped me, no negative impact. If we need some for the development back tracking it is there.
Branching and merging is a wonderful feature, this will give you a great positive impact in your organization, since developers can work there own without dependency then merge there code as needed.
Pull request and review are very great, this will give the efficiency of the developer.

Usability

GitHub is a great tool to use when you have a project or product. Branching is a very good feature, for different clients you can keep different versions of the application. If a common fix is needed you can always do it once and do cherry picking. This way your other part of the code won't be affected. Also the labelling will gives the hierarchy.

Alternatives Considered

GitLab and Mercurial

Comparing between GitHub, GitLab and Mercurial, I felt real hard to work with Mercurial, since the application interface was really bad. Bug GitHub and GitLab windows applications were too great compared to Mercurial. If I have to compare between GitLab and GitHub, Most of the area GitLab is Infront. But main issue is, it is very behind compared to community size when comes to GitHub. There are so many open source projects available in GitHub, GitLab have still more room for improvement.

Key Insights

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

Other Software Used

GitLab, Mercurial, Atlassian Bitbucket

Likelihood to Recommend

Other that some minor improvement as I mentioned in the previous question, GitHub is a great tool which can be used to transcend your development + code maintenances good experience. It is easy to back track through the changes since the revisions are available. Also we can see what are the available branches, how many I created etc. This also helps to get a overall idea what is going on.

GitHub Feature Ratings

Comments

Please log in to join the conversation

My Honest Review On GitHub

Software Version