Open Mrjoy832 opened 2 years ago
✅ Good to go😎🤩
✅ Good to go😎🤩
Pata hain 😤😤
All Set To Go✅✅
PR{s)
Write descriptive and consistent names
Create a clear PR title and description
Keep PRs short (same applies to files and functions)
Branch(s)
The important branches in any project is the
-Main - Stable version
-Development - Where all the changes take place
-QA - Where all the testing takes place
The branches we will be working on has to be named as per a standard. For example, the branch name can include words
like
bug, fix, WIP, etc, the issue it will be solving, author name, etc.
The name of these branches should match with the naming convention of the rest of the team.
Issue(s)
Always see for good-first-issue in the repos Avoid long descriptive names Create only meaningful issues
I am going to contribute into learnCPP which was under GSSOC'22. I am already assigned on this issue and going to start working on it. The issue: C++ code to find out cycle in a linked list. Link: https://github.com/Lakhankumawat/LearnCPP/issues/415
I am assigned to an issue , start working and searching the solution of the issue https://github.com/Lakhankumawat/LearnCPP/issues/415
All Set To Go Verified for Milestone-3 Congrats👍
PR/MRs must be created between October 1 and October 31 and PRs must be made to public, unarchived repository. PR/MRs that their system detects as spammy will also not be counted. User with two or more spammy PR/MRs will be disqualified. PR/MRs must be tagged “HACKTOBERFEST” or must be labeled “HACKTOBERFEST-ACCEPTED". PR/MRs must not be labeled as "INVALID". PR/MRs Must be merged or have an overall approving review.
Not done challenge 28 29 and 30
name: Tridib Bag github_user_name: Mrjoy832