Please note that this project has a Contributor Code of Conduct. By contributing in this project you agree to abide by its terms.
- create a useful title for your pull request. Don't use 'Updated readme file'.
- Check the other resources in the readme list to avoid duplication.
- Use a Captial letter at the beginning of your title or description and use a period at the end of your description.
- Check your spelling and grammar before submitting any request.
- Make individual request for every github repo you want to add.
- This list is limited to web development resources.
- You can add github repos for different JS frameworks like repos with react matterial only.
- Use the folllowing format [title](link of the repo) - Description of what the repository contains in one or two sentences.
- Be respectful in your commit messages.
- List should be addedalphabetically.
-
Fork the repo and clone the forked repo on your local development environment.
-
Create a branch using
git checkout -b feature/<feature-name>
git checkout -b feature/<adding-vue-resource>
git checkout -b bug/<bug-name>
-
Name the branch according to what it does (e.g.: feature/added-react-resource)
-
Add the Github repository with the resources in the readme file.
-
Use the folllowing format
[title](link of the repo) - Description
- Description of what the repository contains in one or two sentences.. -
- Stage all the changes using -
git add .
- Commit the staged changes using -
git commit -m "your commit message"
. Make sure to write meaningful commit messages. - Before you push the commit make sure to pull the changes in the remote branch using
git pull origin develop
, in case of conflicts, please resolve them. - After pulling the changes, push the all the changes using
git push origin branch-name
- Stage all the changes using -
-
Create your PR into the
Develop branch
(not main branch) -
Go to this current Repository.
-
Create a Pull Request against the
develop
branch, make sure you don't make PR against themain
branch. -
Write the Issue Number in the description if the pull request is related to some issue.
-
Leave a short message in the PR explaining in slightly more detail what the PR accomplishes.
-
If your PR touches multiple parts, consider adding a bullet list of accomplishments.
-
Amazing you just made your first successful Pull request. Just wait a few minutes for me to merge it.