📌New API is the one where all the endpoints are defined by you and there is no integration of any API that's already existing.
📌Existing API means that there is an API that is already existing, you are just fetching data and displaying it from an external source.
✅If you are contributing towards enhancement of any API, you need to make sure that you are enhancing at least 2 APIs.
✅If you are contributing towards any documentation related bug, you should solve at least 5 documentation bugs to get your PR merged.
Here you go🚀, Looking towards great contributions from your side!🔥
Happy Coding!❤️
- Go through the project README.md and CONTRIBUTING GUIDELINES to know about the project and related guidelines.
- Go through the project to know what you can contribute towards it.
-
CREATING ISSUE!
-
Under the issues section, you can select a proper template, and fill all the necessary details.
YOU ARE NOT SUPPOSED TO ALTER THE PROJECT TITLE. ISSUE TITLE SHOULD BE MENTIONED AFTER []
. -
You have to wait till the issue is assigned to you. After the issue is assigned, you can start working on the issue.
-
-
ADDING YOUR CODE!
- You need to fork the repository to work on the project.
- After forking into your account, you need to clone it using
git clone "repo_link"
- After cloning the repository, you need to create a new branch
git checkout -b <BRANCH_NAME>
- Add the code that you want to contribute from your side under the newly created branch.
- Make sure you follow proper file structure. If you are creating a new API, then you should add your folder(
NAMEOFAPI
) into theNew_APIs
folder. If you are adding any existing API, make sure proper file structure is followed and you have addedREADME.md
files for the APIs you are adding.
-
BRINGING YOUR CODE ON GITHUB!
git add .
to stage your changes.- Use
git commit -m "message"
to commit the changes. Make sure you are on the branch you have created. - Push your changes into github using
git push origin <BRANCH_NAME>
. - Once you are done pushing, create a PR and you are done!😎💗🎯