Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hacktoberfest Sign In Sheet 2017!
The goal of this repo is to help beginners who are doing their first pull requests. Feel free to join!
Instruction
In the index file, look for the 'ol' tag. Then insert a 'li' tag with your link to your profile.
Git and Pull Request Resources
Github
The Net Ninja
Awesome-Git
How to Create a Pull Request
Click on the fork on the top to fork this repo.
Go to your repo where you forked the project.
Hit the clone button on your forked repo and copy the given link.
On your terminal / command prompt, type "git clone [put the link here]".
Change the index file in the folder.
Afterward, on your terminal / command prompt, type "git add index.html"; then 'git commit -m "[type a message]" '.
Create a remote to link the repository on github to your local workspace. use "git remote add [remote-name] [put the github link here]"
Push the commit. For example, type "git push [remote-name] master".
Go back to the original repo.
Hit "new pull request" and compare between forks.
Confirm the pull request and that's it!
#Info (delete this section)
Please see the contributing guide, on the contributing section.
You should notify the maintainers on the issue you are working on before you send a PR.
Rebase and
squash your commits.
Submit one commit only, on top of the branch you are working on,
master
for bug fixes to thestable version,
vnext
to new analyzers and fixers.Verify if you pass the definition of done.
Always reference issue you are fixing (see bellow, e.g.
Fixes #123
)#Start your PR description here (delete this line too)
Fixes # .