A new blog post - How to get started contributing to GitLab by example
Triage (REQUIRED)
Please note that there is a different process for when you want to announce something via the blog. Please see announcement requests in the handbook and open an announcement request issue instead of a blog post issue.
Proposal
I would like to add a blog post about my experience with the very first contribution to GitLab. It will describe my approach to joining a new project:
- Local dev environment setup
- Picking up the first issue
- The journey of solving the issue
- MR creation and code review experience
- Debugging tools setup
The goal would be to guide new contributors and inspire them to get started.
Checklist
-
Does this align with a time-sensitive release, campaign or announcement? Please add link to pertinent info such as eBook landing page -
If wide-spread customer impacting or sensitive, mention @lboughner
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @mjoscelyn
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
If the post is about one of GitLab's customers, mention @nicolecsmith
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if this post requires additional approval from internal or external parties before publishing (please tag needed sign off DRIs as necessary) -
Please upload any images to the MR before tagging the editorial team.
Questions?
-
Please tag @Sgittlen with any questions/concerns/confusion.