I remember officially switching my professional career from being a Linux system administrator to a Python software engineer. It was ten years ago when I decided that rebooting servers was dull. Watching the software engineering team working next to me, seeing them doing git commit -a -m 'friday night
GitHub makes collaborating with many different people on a single piece of code or software much easier by managing the details involved in version control alongside your project's evolving history. This makes it especially useful for comparing code changes as they come in and sorting out differences between
Choosing a distribution license for the software you publish on GitHub can seem confusing at first. After all, there are quite literally hundreds of licenses [https://spdx.org/licenses/] to choose from, all of which are suitable for different purposes and grant users of your code unique rights. For first-time
The second quarter of 2021 has finished. As usual, we got pretty busy and shipped a lot of new features. This quarter has been marked by a massive increase in our number of users and, therefore, our workload. We spent quite some time preparing for significant improvements in our processing
Adopting the right code review best practices can drastically speed up your review process while also improving the quality of your reviews. Often enough, code reviews can become areas of contention among members of your team, prompting them to become defensive about work they’ve done or changes they may
GitHub merge methods can be tough to choose correctly. Implementing the wrong merge method on your project's main branch can detract from your team's ability to follow along and contribute. In other words, using the wrong merge method for the occasion defeats the entire purpose of
Good commit messages make a big difference in your team's ability to stay on top of changes to your codebase. However, coming up with useful and understandable messages is often easier said than done, especially when you’re hard at work. Luckily, there are a few tricks to
Managing security updates on GitHub can get hectic in a hurry as third-party dependencies develop at their own pace, separate from your project. Leaving vulnerable dependencies unpatched can open your entire application up to otherwise avoidable threats, but manually reviewing and merging such updates can quickly eat up all of
GitHub Actions are a collection of tools that help you streamline your development workflows through automation. These actions are event-driven, meaning they’ll trigger upon certain things happening. There are tons of GitHub Actions you can use—here are some of the best. 1. Checkout Everybody knows about Checkout [https:
Do you happen to know the common point between the open-source Node.js and Rust projects, the sporty social network Strava, the e-commerce company Shopify and the ride-hailing company Uber? Their engineering team all rely on a merge queue. Well, if you never heard of such a concept, you might
Once developers have completed work on project features and you’ve approved their pull requests [https://blog.mergify.com/what-is-a-pull-request/], it’s time to merge those requests into the main project repository. When doing so, Git has to find a base commit shared by two or more commits and then
We all knew it was going to happen anyway. GitHub just pulled the plug and removed Dependabot Preview. Dependabot was absorbed by GitHub 2 years ago now, and it seemed logical to phase out the Preview version of it. More than 30,000 organizations relied on this fabulous tool to