Need advice about which tool to choose?Ask the StackShare community!
Yours thankfully, Darkhiem
Hey there, Definitely install Git. Git is the open source version control system that both GitHub and GitLab interface with. Git is extremely important as a new developer to learn, and once you do, you will be so thankful you are tracking your projects in it. Git makes it super easy to track changes you make in your code, and even rollback, edit, view, or delete changes you made months before. In software development, it is a crucial skill to learn.
GitHub and GitLab are online cloud Git repositories. They are for backing up your repos in the cloud, and working with other developers, or even working with yourself via other devices. I would recommend starting with GitHub since you are a new developer. Companies will want to see your GitHub when you start applying to jobs, and having one will be a great plus going for you. It also is the most widely used by developers and most open source projects are hosted on GitHub.
Here is a course on Codecademy to start learning: https://www.codecademy.com/learn/learn-git
Hope this helps! Good luck!
I think Github is the most important thing, so take good care of it, and share your most important programs on it with others, this helps to raise your efficiency through the feedback of others. with my Greetings.
Hey! Regardless of your choice of platform, you will need to install and learn Git. So start there! The differences between GitHub and GitLab are not relevant to you at this stage.
I use GitHub by few years. For now, I think this is the best way to work on another computers or to work with other people. I tested GitLab and Git, but for me GitHub is easier and most friendly for another developers who are worked with me.
For python, Pycharm is a very nice and beginner friendly IDE. I am using it myself, use the free community edition, it also comes with a lot of great tools.
I would like some information regarding the benefits an aspiring start-up company may have, while using GitHub Enterprise vs the regular GitHub package. On a separate issue, I'd like to understand whether GitLab may have some DevOps-related advantages GitHub does not.
Thank you in advance, Matt
I'd lean towards GitHub (either billing plan) for one key reason that is often overlooked (we certainly did!).
If you're planning on creating OSS repositories under your start-up's name/brand, people will naturally expect to find the public repositories on GitHub. Not on GitLab, or Bitbucket, or a self-hosted Gitea, but on GitHub.
Personally, I find it simpler to have all of the repositories (public and private) under one organisation and on one platform, so for this reason, I think that GitHub is the best choice.
On the DevOps side, GitLab is far superior to GitHub (from my experience using both GitHub Enterprise and GitLab Ultimate), but for the one aforementioned, we're using GitHub at Moducate.
Advantages for Github Enterprise is that you get more storage, CI minutes, advanced security features, and premium support. If you don't really need any of those, you can stick with Github Team. Though if you're going to use Gitlab CI, I suggest going with Gitlab instead of Github so you won't have to maintain 2 repositories.
Regarding the advantages that Gitlab CI has over Github, there's a detailed explanation here: https://about.gitlab.com/devops-tools/github-vs-gitlab/ci-missing-github-capabilities/
If you need more minutes for Gitlab CI, you can always use your own Gitlab CI runners instead of the shared runners: https://docs.gitlab.com/runner/register/
With the advent of Gitlab actions/workflows, it's hard to not choose Github anymore. I say that with all love for Gitlab, as it's been my personal tool of choice for a long time because of it's inbuilt CI/CD solutions. Github is just all around more adopted by the community so you'll always find more support; and if you go with enterprise you will get 50k build minutes a month as well as a ton of extra tools that will definitely help a startup out from the get-go. That being said, it's priced at $21 per user, per month so if you cannot afford that, I say go with Github.
GitHub Enterprise comes with included SAML SSO support, and a huge free tier for Actions and Packages, which gives your team everything they need to get off to a great start and scale up without hitting any roadblocks along the way. An important point to consider is that GitHub Enterprise comes in both self-hosted and cloud-hosted variations, so you don't need to manage your own infrastructure for it unless you would prefer to.
With GitHub Enterprise, you also plug in to the largest development community in the world, and can collaborate directly on the open source projects that are probably already part of your stack. You can also access the latest and greatest in development tools such as GitHub Codespaces, GitHub Co-Pilot, and much much more, with great new features being shipped every day.
GitHub is trying to catch up with GitLab. GitLab was built from the ground up with DevOps tooling. GitHub is years away on features.
Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.
Now I want advice on below.
- Is it a good idea to migrate from Bitbucket to AWS Codecommit?
- If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
Hi Kavita. It would be useful to explain in a bit more detail the integration to Jira you would like to achieve. Some of the Jira plugins will work with any git repository, regardless if its github/bitbucket/gitlab.
We chose github + github actions in order to manage the code versioning and the CI on the same software. Furthermore, while it is not that much, I believe that for a large team it is considerably cheaper to have one github subscription instead of a git subscription and a CI/CD software subscription.
GitHub provides great user experience ans most developers are familiar with it. There is also an attractive pricing model for those who already have a Visual Studio subscription.
We also don't like the "everything in one tool" approach from GitHub as there are better tools for build system, package registries, etc. on the market.
We chose GitHub for version control hosting because of its high-quality and performant pull request user interface, as well as GitHub Actions.
We also selected GitHub as our first OAuth2 authorization provider because of its large community, high-quality documentation, and sophisticated App framework for granular permission management and event notifications.
The company needed to move from hosting all of our repositories, tickets & releases from a GForge instance hosted by our former parent company. The decision was made to move to GitHub Enterprise but the developers were not told until there was 1 month left to go. So needed something that could pull all of our information out and push it to the new hosts and it needed to be done ASAP.
Do you have a K8s cluster and you want to deploy some services to it? Gitlab Auto Devops is key to achieve this without breaking a sweat.
We deploy Go services to our K8S clusters with warp speed thanks to Gitlab and it's Auto Devops pipeline.
I haven't seen tooling like this in any other git cloud provider.
Both of us are far more familiar with GitHub than Gitlab, and so for our first big project together decided to go with what we know here instead of figuring out something new (there are so many new things we need to figure out, might as well reduce the number of optionally new things, lol). We aren't currently taking advantage of GitHub Actions or very many other built-in features (besides Dependabot) but luckily it integrates very well with the other services we're using.
I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.
I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.
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.3K
- Great for team collaboration1.1K
- Easy setup865
- Issue tracker504
- Great community485
- Remote team collaboration481
- Great way to share451
- Pull request and features planning442
- Just works146
- Integrated in many tools132
- Free Public Repos120
- Github Gists115
- Github pages111
- Easy to find repos83
- Open source62
- It's free60
- Easy to find projects60
- Network effect56
- Extensive API49
- Developer Profiles34
- Git Powered Wikis32
- Great for collaboration30
- It's fun24
- Clean interface and good integrations23
- Community SDK involvement22
- Learn from others source code20
- Because: Git16
- It integrates directly with Azure14
- Standard in Open Source collab10
- Beautiful user experience8
- It integrates directly with Hipchat8
- Easy to discover new code libraries7
- Smooth integration6
- It's awesome6
- Nice API6
- Cloud SCM6
- Hands down best online Git service available5
- CI Integration5
- Quick Onboarding5
- Remarkable uptime5
- Security options4
- Simple but powerful4
- Loved by developers4
- Easy to use and collaborate with others4
- Version Control4
- Unlimited Public Repos at no cost4
- Uses GIT4
- Free HTML hosting4
- Nice to use3
- Free private repos2
- Issues tracker2
- Easy deployment via SSH2
- Easy source control and everything is backed up2
- IAM integration2
- Easy and efficient maintainance of the projects2
- All in one development service2
- Good tools support2
- Free HTML hostings2
- Self Hosted2
- Never dethroned2
- Very Easy to Use2
- Easy to use2
- Leads the copycats2
Pros of GitLab
- Self hosted505
- Has community edition338
- Easy setup241
- Familiar interface239
- Includes many features, including ci136
- Nice UI112
- Good integration with gitlabci83
- Simple setup56
- Has an official mobile app34
- Free private repository33
- Continuous Integration30
- Open source, great ui (like github)21
- Slack Integration17
- Full CI flow13
- Free and unlimited private git repos11
- User, group, and project access management is simple9
- Intuitive UI8
- All in one (Git, CI, Agile..)8
- Built-in CI7
- Full DevOps suite with Git5
- Both public and private Repositories5
- Build/pipeline definition alongside code4
- Integrated Docker Registry4
- Mattermost Chat client4
- Issue system4
- It's powerful source code management tool4
- So easy to use4
- Low maintenance cost due omnibus-deployment3
- Security and Stable3
- I like the its runners and executors feature3
- It's fully integrated3
- Unlimited free repos & collaborators3
- Great for team collaboration3
- Free private repos3
- Because is the best remote host for git repositories3
- One-click install through DigitalOcean2
- Review Apps feature2
- Built-in Docker Registry2
- Powerful software planning and maintaining tools2
- Multilingual interface2
- Groups of groups2
- Not Microsoft Owned2
- Published IP list for whitelisting (gl-infra#434)2
- Kubernetes Integration2
- Many private repo2
- HipChat intergration2
- The dashboard with deployed environments2
- Native CI2
- It includes everything I need, all packaged with docker2
- Kubernetes integration with GitLab CI2
- Powerful Continuous Integration System2
- Supports Radius/Ldap & Browser Code Edits1
Pros of Gogs
- Self-hosted github like service36
- Very low memory footprint31
- Easy to install / update29
- Lightweight (low minimal req.) runs on Raspberry pi17
- Single binary deploy no dependencies16
- Open source14
- Cross platform (MacOS, Windows, Linux ...)12
- Issue tracker10
- Great UI3
- LDAP Support3
Sign up to add or upvote prosMake informed product decisions
Cons of GitHub
- Owned by micrcosoft53
- Expensive for lone developers that want private repos37
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos8
- Limited featureset for issue management3
- GitHub Packages does not support SNAPSHOT versions2
- Does not have a graph for showing history like git lens2
- Have to use a token for the package registry1
- No multilingual interface1
- Takes a long time to commit1
Cons of GitLab
- Slow ui performance28
- Introduce breaking bugs every release8
- Insecure (no published IP list for whitelisting)6
- Built-in Docker Registry2
- Review Apps feature1
Cons of Gogs
Sign up to add or upvote consMake informed product decisions
What is GitHub?
What is GitLab?
What is Gogs?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with GitHub?
Sign up to get full access to all the tool integrationsMake informed product decisions