@saisharan512 contributor onboarding

🌟 Welcome to your GitLab contribution journey! 🌟

🎉 Welcome to the GitLab Community! 🎊

Hey @saisharan512! 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 community forks access request and help you get started.

🚀 Your contribution adventure

Welcome to your GitLab contribution quest! You've already taken the first step by requesting access - now let's explore what's next on your path to becoming a contributor!

🎬 First steps

• Request access to the community forks.
  • Our maintainers will reach out if they need more info to approve your request.
  • Watch for the access-requestapproved label once your request has been approved.
• Say hello in the community Discord #contribute channel. 👋
  • Add your Discord ID to your GitLab profile and earn points for your posts and replies!
• 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 after your access is approved.

🛠️ Make your first 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!

🚀 Keep the momentum going:

1. Choose your path:
   • Use the issue finder to find and assign a quick win issue to yourself, or
   • Find a different issue and assign yourself using the manage issue page. Only assign issues to yourself that meet the following criteria:
     • Have an implementation plan
     • Unassigned
     • Labeled ~workflow::ready for development
2. Follow the implementation plan provided.
3. Create your merge request using a community fork.
4. Follow the review process to get your work merged!

🔄 Repeat for future contributions

🤝 Need help?

• Reach out in the community Discord #contribute channel.
• Type @gitlab-bot help in a merge request or issue to tag a Merge Request Coach.
• Join community office hours to ask questions, troubleshoot your development environment, and learn from others. 👥

🏆 Level up your impact

• Explore the GitLab Contributor Platform to track your impact. 📊
  • View your contribution metrics and achievements on your personal dashboard. 🏅
  • Track your progress on the global contributor rankings. 🏆
  • Showcase your organization's impact on the company leaderboard. 💫
    • Hint: update your profile, adding your company name under Organization.
• Help label and close some unlabelled issues.
  • Paste the issue URL into our issue management page.
  • Classify the type (feature, bug, or maintainenance) and product group with help from GitLab Duo AI.
  • Close anything no longer relevant (solved, not reproducible, or a support request).
• Join our next GitLab Hackathon. 🎪
• Keep the momentum going:
  • Try another quick win.
  • Create your own issue. 💡
  • Explore our other exciting projects:
    • cli 🖥️
    • GitLab Terraform Provider ⚡
    • GitLab Runner 🏃
    • gitaly 🔄
  • Help build the CI/CD components catalog:
    • CI/CD components 📖
    • Development guide 🔧