Every day, many projects use Mergify to automate their GitHub workflow. Independently of their team size, the one thing they all have in common is that the project leads are willing to let their developers focus on what’s really important—code. So we decided to meet with some of them to learn more about the challenges they face and discover how Mergify helps them be more efficient when it comes to pull requests. This time, we talked to Oleg, aka iamolegga.
Can you tell us more about you and your project?
I am a Software Developer for more than 10 years. I'm currently living in Cyprus.
In my spare time, alongside my job, I work on a number of open source projects centralized on iamolegga.
I mainly work on NestJS, React Native and GO, developing modules. Some of them are quite successful for its audience. For example nestjs-pino (a platform agnostic logger for NestJS based on pino with request context in every log) is downloaded over a million times a month.
Are you alone on this project?
Most of the time, I'm working alone on my Open Source project. However, some guest contributors open new pull requests from time to time.
My projects are not that collaborative, I work on them and make them accessible to others developers.
What were your pain points?
Actually, there was only one pain point: updating dependencies.
Most of my projects have only development dependencies. On those, everything was fine.
However, on some, there are dependencies with third-party libraries (maybe 10 in total) and updating these dependencies was complicated.
I didn't have a lot of time, so I rarely updated them. I did it when I thought of it, when I had the time and the inclination.
I only updated them when there was a major update.
Can you tell us more about how you found Mergify?
I discovered Mergify a long time ago, several years ago, by reading a blog post on dev.to. A guy was speaking about Mergify. I couldn't say which one , but that's how I came to know Mergify. That's when I discovered the concept of Merge Queues.
In this article, a developer presents his workflow in detail. In particular, he explained how he went about updating dependencies. I identified myself quite easily, since this was a problem for me.
Was it easy to set up?
It couldn't have been easier. In the article I'm talking about, the author shared his Mergify configuration. All I had to do was copy and paste it, and it was done. Maybe I made a couple of changes, but I'm not even sure.
Did Mergify help you with your pain points?
Absolutely, when I found this article, I immediately installed Mergify.
At the same time, I also installed Dependabot and everything ran like clockwork.
And it automated everything on the rests where it was installed. It's pure automation, and it saved me time and therefore productivity.
Once it's installed, you tend to forget about it, and everything takes care of itself.