Experienced software engineer, you have a good technical background and you want to move on, these articles are for you.
Technical
Continuous Integration, Continuous Delivery and Continuous Deployment are like vectors pointing to the same direction but having different magnitude. The factor which makes them point in the same direction is the goal to make our software development process faster and more robust. Continuous Integration, Continuous Delivery and Continuous Deployment all
Technical
Bob, after conversing with Jenny, learned about GitOps and is using it effectively. Previously what took him 8-12 weeks to develop due to operations issues can now be resolved in days. Every other week Bob builds a new version of his application. At some point, Bob's user base
Tutorials
If you never heard of Phabricator, you might not be alone. I admit I only started to hear about it recently, while the project started in 2010. Phabricator is essentially a forge, a suite of web-based developments collaborators tools, including multiple tools to do code reviews, track bugs or browse
Basic Knowledge
Meet Bob, a software developer from France. Being a senior developer and working in a startup, Bob develops, deploys, and maintains his application on his own. Until the point when he came to know about GitOps, he maintained deployment pipelines which also had a lot of manual processes and requests
Tutorials
GitHub Actions is powerful and allows you to run various workflows on your pull requests. There is an entire marketplace of actions that you can use, reuse, and abuse. GitHub Actions became a defacto standard for many developer teams that want to run jobs when creating a pull request. This
Technical
Merge queues are at the center of the value offered by Mergify. The freeze feature we announced [https://blog.mergify.com/announcing-merge-queue-freezes/] a few days ago gives our merge queues a whole new range of possible use cases. You can now make your queues follow your product development life cycle.
Tutorials
Merge queues are a core component of Mergify. We implement new features regularly to provide new use possibilities. Their core mechanics also need to be adapted to support such evolutions. While testing and ensuring that any pull request fits perfectly into the main branch, time is a dimension that can
Technical
As you may guess, Mergify relies a lot on third-party APIs like the Stripe API [https://stripe.com/docs/api] or the GitHub API [https://docs.github.com/en/rest] and their behavior. Like any third-party service, we need to deal with many things to ensure our integration never breaks.
How We Do It
Since its inception, the Mergify [https://mergify.com] engineering team decided to focus on its product and not spend time building infrastructure. It made a lot of sense as we started as a small team of two engineers with low resources and that the first version of Mergify was an
Technical
While Linus Torvalds is well-known for Linux, he's also reputed for not having his tongue in his pocket. He is often complaining loudly about what he thinks is wrong or damageable to the industry. As the creator of Git 15 years ago, it's interesting to hear
Tutorials
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
Best Practices
Last September, GitHub launched GitHub CLI 1.0 and brought GitHub to the terminal. GitHub CLI is GitHub command-line interface. It brings pull requests, issues, and other GitHub concepts to the terminal next to where you are already working with Git and your code — according to its documentation [https://cli.