Yesterday my very first DEV PR got merged!
I didn't have any experience in Ruby so I wanted to do something easy, I came across this Issue/Feature request from @jess.
3 year badge #1562
Is your feature request related to a problem? Please describe. Let's award 3 year badges when members hit their 3 year mark!
Even though the Issue wasn't approved
yet I felt pretty confident that it wouldn't be an issue because it was a suggestion from a DEV co-founder 😂
The PR itself was fairly easy, I could base my code on the already available 2 year anniversary badge with little changes required.
Added 3 year anniversary badge #1732
What type of PR is this? (check all applicable)
- [ ] Refactor
- [X] Feature
- [ ] Bug Fix
- [ ] Documentation Update
Description
Added 3 year anniversary badge, I hope to get this badge some day
Related Tickets & Documents
Closes #1562
Mobile & Desktop Screenshots/Recordings (if there are UI changes)
Added to documentation?
- [ ] docs.dev.to
- [ ] readme
- [X] no documentation needed
[optional] What gif best describes this PR or how it makes you feel?
After that the PR got reviewed and merged very quickly by @ben.
I hope to stay in this awesome community long enough to receive this badge!
This is my very first blog post on DEV (and first blog post in general) I hope to not only lurk and comment but in the future make more blog posts, also a little more technical posts.
And besides my very first DEV PR and post I have also received my very first DEV Badge! 🎉
Top comments (13)
This was one of those tasks I was sure we were going to put off for way too long.
We still don't have a four-year badge designed, but I feel like this part of the code now could probably be refactored to account for an arbitrary number of years, and maybe take an environment variable to determine how many to iterate through.
Anyone who wants to refactor this so we don't need to add a new method every year is welcome to submit another PR at some point in the next 11 or so months. 😄
Interesting, this would indeed be a good improvement to be more future proof. Only thing you still would need to do is prepare the designs for the upcoming years but you could make a couple at once so you will be good for a few years 😉
I am triggered by this challenge but am afraid that my knowledge in Ruby isn't good enough right now.
I'd guess something like this
Though I don't really know ruby either 😅
I'm not sure this line would work as expected
This week my second dev.to pr merged. I’m so happy. This makes me feel better. Being part of the dev.to contributors is awesome.
Thanks @ben
dude!! So awesome! You totally encouraged me to try this myself. I literally looks at the repo the other day and was going to fix an issue (also not a ruby dev) but I was like... no they probably won't want me to. Thanks to you, I know I should!
Awesome! I never expected that I was going to encourage anyone to contribute with my small PR and post 😂 But so happy that I did!
I thought the same in the past with a Node project (cdnjs.com) after a year, during Hacktoberfest, I finally did it and it was a lot of fun. I have tried different small projects/tweaks in the past, python, node and now ruby, always fun to step out of your comfort zone and just mess around.
Ya! you made a big step today. I was blown away by what happens when you put yourself out there. It helps others, so thank you!
Congrats Glenn on getting your first PR merged! 🔥
Thanks! It wasn't that big of a change and I am sure anyone could have done it but it still feels great to be able to contribute to this community.
Good stuff!
Nice! I had one merged a couple weeks ago too. Feels good man.
Welcome to the PR-ty ! ☜(゚ヮ゚☜)
I'll_see_myself_out_
Awesome PR! Everyone needs a little music in their life 😉
Congrats!! Keep it up and treasure that feeling to keep going :)