Skip to content

@krasotkatasha contributor onboarding

🌟 Welcome to your GitLab contribution journey! 🌟

Reason: 
Interests: ux
Languages: 

🎉 Welcome to the GitLab Community! 🎊

Hey krasotkatasha! 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) 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

  • Start onboarding.
  • Say hello in the community Discord #contribute channel. 👋
  • Join our next GitLab 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.
Read about other ways to contribute

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, 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 so we can link your accounts.

Supporting others

There are many ways you can contribute to the GitLab community by supporting other members:

  • Answer questions in Discord.
  • Answer questions on the Forum.
  • Label/close/validate issues.

📅 Content and events

If you are speaking about GitLab at an event, or have organized an event about GitLab, please submit details.

Similarly, if you have created any content (for example, blog posts, or video content), please submit details.

🛠️ Make your first code contribution

  1. Find a First-time contributor issue. 🌱
  2. Add a comment to the issue you would like to work on along with any thoughts or questions.
  3. Pick your development environment.
  4. Follow the implementation plan provided.
  5. Create your merge request using a community fork.
  6. Follow the review process to get your work merged!

🔄 Repeat for future contributions

⚙️ CI/CD Components

We recognise contributions to GitLab managed CI/CD components in our CI/CD catalog.

We need help recognising non-GitLab managed components.

🤝 Need help?

🏆 Level up your impact

Edited by Наталія Кривенко