Contribution Guidelines
🏗
1. Make sure to make UI consistency while adding new features to musicify
2. Use the packages which are compatible with our website.
3. Make sure that your code is well documented to be easily readable and understandable, especially in tougher areas.
4. Use the uniform naming convention throughout the codebase.
5. Make sure that the code is as modular as possible.
6. Separate UI and logic part
7. Do not spam unnecessary merge requests.
1. Fork this repository.
2. Clone your forked copy of the project.
git clone https://github.com/<your_user_name>/musicify.git
3. Navigate to the project directory
cd musicify
4. Add a reference(remote) to the original repository.
git remote add upstream https://github.com/PRINCE-DHAMECHA/musicify.git
5. Check the remotes for this repository.
git remote -v
6. Always take a pull from the upstream repository to your master branch to keep it at par with the main project(updated repository).
git pull upstream main
7. Create a new branch.
git checkout -b <your_branch_name>
8. Perfom your desired changes to the code base.
9. Track your changes
git add .
10. Commit your changes .
git commit -m "Relevant message"
11. Push the committed changes in your feature branch to your remote repo.
git push -u origin <your_branch_name>
12. To create a pull request, click on **compare and pull requests**.
13. Add appropriate title and description to your pull request explaining your changes and efforts done.
14. Click on Create Pull Request.
15. Voila
16. Congratulations! You've made your first contribution!
For further details, click on CONTRIBUTING.md
Code of Conduct
We follow certain guidelines in order to maintain this repository. Please find our code of conduct and read it carefully.
Who are the makers of musicify?
🤓
 |
 |
 |
|---|---|---|
8 Nov 2, 2022
1 Jan 3, 2022
9 Jun 14, 2022
20 Oct 4, 2022
26 Aug 9, 2022
18 Oct 29, 2022
5 Jan 4, 2023
8 Sep 4, 2022
5 Nov 24, 2022
22 Oct 5, 2022