Hi friends, since many of you are starting to contribute for Hacktoberfest.
To not disallow beginners to contribute to the project, this issue can be taken up by anyone starting to learn data structures and algorithms.
You need to start solving the problems in the Hackerrank's Tracks and add your solutions in the branch named trackname in a new folder with your github username.
For example, if I am solving the problems in the Interview Preparation Kit here, then there is a branch in the project with the name interview_preparation_kit, so I will create a folder in that named sahilbansal17 and start adding the solutions in that folder.
In every pull request, at least 4 solutions should be there. We will mark invalid all those pull requests having less than 4 solutions.
Make sure that your solutions are well commented, do not use any macros, quite readable, properly indented and organized in proper folders (if the track has any categorization, for e.g. interview preparation kit has separate topics like Arrays, Sorting, etc. so folders with these name can be created inside your folder in the branch.
Note: If the branch doesn't exist for the track you wish to contribute (say, problem solving, then comment in the issue. The branch will be created.
Hi friends, since many of you are starting to contribute for Hacktoberfest.
To not disallow beginners to contribute to the project, this issue can be taken up by anyone starting to learn data structures and algorithms.
You need to start solving the problems in the Hackerrank's Tracks and add your solutions in the branch named trackname in a new folder with your github username.
For example, if I am solving the problems in the Interview Preparation Kit here, then there is a branch in the project with the name interview_preparation_kit, so I will create a folder in that named sahilbansal17 and start adding the solutions in that folder.
In every pull request, at least 4 solutions should be there. We will mark invalid all those pull requests having less than 4 solutions.
Make sure that your solutions are well commented, do not use any macros, quite readable, properly indented and organized in proper folders (if the track has any categorization, for e.g. interview preparation kit has separate topics like Arrays, Sorting, etc. so folders with these name can be created inside your folder in the branch.
Note: If the branch doesn't exist for the track you wish to contribute (say, problem solving, then comment in the issue. The branch will be created.