Need advice about which tool to choose?Ask the StackShare community!
GitHub vs Sonatype Nexus: What are the differences?
Developers describe GitHub as "Powerful collaboration, review, and code management for open source and private development projects". GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. On the other hand, Sonatype Nexus is detailed as "The world's best way to organize, store, and distribute software components". Deliver better, safer software even faster with software supply chain automation.
GitHub belongs to "Code Collaboration & Version Control" category of the tech stack, while Sonatype Nexus can be primarily classified under "Java Build Tools".
Sonatype Nexus is an open source tool with 527 GitHub stars and 237 GitHub forks. Here's a link to Sonatype Nexus's open source repository on GitHub.
Airbnb, Netflix, and Medium are some of the popular companies that use GitHub, whereas Sonatype Nexus is used by MIT, Auto Trader, and Smart.Biz. GitHub has a broader approval, being mentioned in 4714 company stacks & 6100 developers stacks; compared to Sonatype Nexus, which is listed in 49 company stacks and 16 developer stacks.
Do you review your Pull/Merge Request before assigning Reviewers?
If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:
- Pick the correct target branch
- Make Drafts explicit
- Name things properly
- Ask help for tools
- Remove the noise
- Fetch necessary data
- Understand Mergeability
- Pass the message
- Add screenshots
- Be found in the future
- Comment inline in your changes
Read the blog post for more detailed explanation for each item :D
What else do you review before asking for code review?
Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.
SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.
As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?
One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i
is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.
It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.
Pros of GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.2K
- Great for team collaboration1.1K
- Easy setup858
- Issue tracker494
- Great community477
- Remote team collaboration474
- Great way to share443
- Pull request and features planning435
- Just works138
- Integrated in many tools123
- Free Public Repos111
- Github Gists105
- Github pages102
- Easy to find repos80
- Open source59
- Easy to find projects58
- Network effect56
- It's free54
- Extensive API46
- Organizations42
- Branching41
- Developer Profiles33
- Git Powered Wikis31
- Great for collaboration29
- It's fun22
- Community SDK involvement22
- Clean interface and good integrations21
- Learn from others source code18
- Because: Git14
- It integrates directly with Azure14
- Wide acceptance13
- Standard in Open Source collab9
- Newsfeed9
- Large community9
- It integrates directly with Hipchat8
- Fast7
- Beautiful user experience7
- Cloud SCM6
- Easy to discover new code libraries6
- Nice API5
- It's awesome5
- Integrations5
- Graphs5
- Smooth integration5
- Reliable4
- Remarkable uptime4
- Hands down best online Git service available4
- Uses GIT3
- Version Control3
- Easy to use and collaborate with others3
- Quick Onboarding3
- Free HTML hosting3
- Loved by developers3
- CI Integration3
- Security options3
- Unlimited Public Repos at no cost3
- Simple but powerful3
- Nice to use2
- Beautiful1
- Free HTML hostings1
- Self Hosted1
- All in one development service1
- Ci1
- Easy to use1
- Issues tracker1
- IAM integration1
- IAM1
- Easy deployment via SSH1
- Good tools support1
- Easy source control and everything is backed up1
- Leads the copycats1
- Never dethroned1
- Easy and efficient maintainance of the projects1
- Free private repos1
- Profound0
Pros of Sonatype Nexus
Sign up to add or upvote prosMake informed product decisions
Cons of GitHub
- Owned by micrcosoft39
- Expensive for lone developers that want private repos36
- Relatively slow product/feature release cadence14
- API scoping could be better9
- Only 3 collaborators for private repos8
- Limited featureset for issue management3
- GitHub Packages does not support SNAPSHOT versions2
- No multilingual interface1
- Takes a long time to commit1