# 🌟 Welcome to your GitLab contribution journey! 🌟 ``` Reason: Fix a typo Interests: code, doc Languages: ``` ## 🎉 Welcome to the GitLab Community! 🎊 Hey @aecoleman! We're thrilled to have you join our amazing community of contributors! 🤝 This issue will guide you through your journey to becoming a GitLab contributor. Our experienced maintainers ([`@gitlab-community/maintainers/onboarding-maintainers`](https://gitlab.com/groups/gitlab-community/maintainers/onboarding-maintainers/-/group_members?with_inherited_permissions=exclude)) will review your request and help you get started. ## 🚀 Your contribution adventure Welcome to your GitLab contribution quest! You've already taken the first step - now let's explore what's next on your path to becoming a contributor! ## 🎬 First steps - [X] Start onboarding. - Our maintainers will reach out if they need more info to [approve your request](https://gitlab.com/gitlab-community/meta/-/blob/main/README.md?ref_type=heads#approve-an-access-request). - Watch for the ~access-request::approved label once your request has been approved. - [ ] Say hello in the [community Discord](https://discord.gg/gitlab) `#contribute` channel. 👋 - [ ] Add your Discord ID to [your GitLab profile](https://gitlab.com/-/user_settings/profile) and earn points for your posts and replies! - [ ] Join our next [GitLab Hackathon](https://about.gitlab.com/community/hackathon/). 🎪 - [ ] Experience the power of GitLab Duo - our AI suite including Code Suggestions, Chat, and more! 🤖 - You'll receive your GitLab Duo Enterprise license welcome email once your access is approved. ## 🛠️ Make your first code contribution 1. [ ] Find a `quick-win::first-time contributor` issue using the [issue finder](https://contributors.gitlab.com/issues). **Tip:** Use the filter checkboxes to narrow down issues that match your interests and skills 🌱 **Tip:** You can assign yourself to an issue directly in the issue finder or from the [manage issue page](https://contributors.gitlab.com/manage-issue) ✅ 1. [ ] Add a comment to the issue you would like to work on along with any thoughts or questions. 1. [ ] [Pick your development environment](https://docs.gitlab.com/ee/development/contributing/#choose-a-development-environment). 1. [ ] Follow the implementation plan provided. 1. [ ] [Create your merge request](https://docs.gitlab.com/ee/development/contributing/#open-a-merge-request) using a community fork. 1. [ ] Follow the [review process](https://docs.gitlab.com/ee/development/contributing/#how-community-merge-requests-are-triaged) to get your work merged! 🔄 Repeat for future contributions <details> <summary>Read about other ways to contribute</summary> In your onboarding questionaire, you indicated you were not interested in these contribution types, but here are more details in case you change your mind: ## Translating GitLab For managing the translation process, we use Crowdin. To contribute translations at [translate.gitlab.com](https://translate.gitlab.com/), you must create a Crowdin account. You may create a new account or use any of their supported sign-in services. Ideally, use your GitLab username on Crowdin. If you are unable, complete [this form](https://docs.google.com/forms/d/15XDNFFLhbBJgB4U3u44yRwdiecRAe2ykNl0kRtPFkO0/edit?ts=68000e25) so we can link your accounts. ## :collaboration: Supporting others There are many ways you can contribute to the GitLab community by supporting other members: - Answer questions in [Discord](https://discord.gg/gitlab). - Answer questions on the [Forum](https://forum.gitlab.com). - Label/close/validate issues. ## :date: Content and events If you are speaking about GitLab at an event, or have organized an event about GitLab, please [submit details](https://contributors.gitlab.com/users/me#add-event). Similarly, if you have created any content (for example, blog posts, or video content), please [submit details](https://contributors.gitlab.com/users/me#add-content). ## :gear: CI/CD Components We recognise contributions to [GitLab managed CI/CD components](https://gitlab.com/components) and non-GitLab managed components in our [CI/CD catalog](https://gitlab.com/explore/catalog).</details> ## 🤝 Need help? - Reach out in the [community Discord](https://discord.gg/gitlab) `#contribute` channel. - Mention `@gitlab-community/maintainers/onboarding-maintainers` here. - Join [community office hours](https://www.meetup.com/gitlab-virtual-meetups/). 👥 ## 🏆 Level up your impact - [ ] Explore the [GitLab Contributor Platform](https://contributors.gitlab.com/) to track your impact. 📊 - View your contribution metrics and achievements on your [personal dashboard](https://contributors.gitlab.com/users/aecoleman). 🏅 - Track your progress on the [global contributor rankings](https://contributors.gitlab.com/leaderboard/aecoleman). 🏆 - Showcase your organization's impact on the [company leaderboard](https://contributors.gitlab.com/organizations). 💫 - Hint: [update your profile](https://gitlab.com/-/user_settings/profile), adding your company name under **Organization**. - [ ] Add your personalized [Contributor Stats Banner](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/showcase-your-contributions/stats-banner) to your GitLab profile. 🎖️ - [ ] Help label and close some [unlabelled issues](https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_asc&state=opened&label_name%5B%5D=None&first_page_size=100). - Paste the issue URL into our [issue management page](https://contributors.gitlab.com/manage-issue). - Classify the type (feature, bug, or maintenance) and product group with help from GitLab Duo AI. - Close anything no longer relevant (solved, not reproducible, or a support request). - [ ] Keep the momentum going: - [Create your own issue](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#creating-an-issue). 💡