DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 964,423 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Hugo Martins
Hugo Martins

Posted on • Originally published at hugomartins.io on

Halftime at Hacktoberfest 2020

Even though shitoberfest threatened to ruin Hacktoberfest 2020, I still pushed forward and I’m participating in it, as usual. I’ve written about my participation in 2016 and 2019. In both I have failed (0 PRs in 2016 and 3 PRs in 2019), I have succeeded in 2018 and it has introduced me to a few open-source projects - for example, pytest.

We are now halfway into Hacktoberfest 2020 and I have submitted 2 PRs - one already approved and another under review. To start, I submitted a quick PR to a project I maintain (awesome-linters) to resolve a simple grammatical error that a user spotted. Since the user didn’t want to open the PR, I ended up creating the PR and accepting it as an Hacktoberfest contribution - all in all I have to maintain it so I thought it kind of made sense.

For a second PR, which is still under review, I tried to contribute something more substantial. Even though it is still a beginner-friendly PR, this PR I opened in pytest aims to improve the reporting of the tool when it is executed with --collection-only. A user reported that it was a bit confusing and I tried to understand where the reporting issue came from and β€œfixed it”. I hope his small 29 LOC PR gets accepted, as it will be my first PR to pytest’s core - I made a few contributions to documentation but not to the core codebase.

Let’s see what I can still do with the rest of Hacktoberfest 2020 but I am already happy about this core contribution to pytest.

Top comments (0)

Find what you were looking for? Join hundreds of thousands of developers on DEV so you can:

🌚 Enable dark mode
πŸ”  Change your default font
πŸ“š Adjust your experience level to see more relevant content