Add Git instructions for how to fork repo and create PR in Contributing.md file

[actuallyyun]

Hi, I think it would be a good idea to have clear and detailed instructions on how to use Git to contribute to this repo in the Contributing.md file. I could create a PR for this. Thank you!

[shrn01]

Hey @actuallyyun, We do have books in the repo that talk about how to use Git. Do we need to have it explicitly here?

[actuallyyun]

Hi @shrn01 Thanks for the reply.

As a newcomer who would like to contribute, my flow was: README.ME →Contributing.md →In a nutshell→ If you know Git, please Fork the repo and send Pull Requests (PR).

I think it would be helpful to have a quick instruction on how to use Git to contribute here, for instance, the command for cloning the repo, command for pulling commits to one's local machine... An example I had in mind, if you go down to Workflow and Pull Requests you could see a protect-specific instruction on how to contribute with Git.

I learned that contributing resources doesn't require opening an issue. I think it would be beneficial to specify this in the file as well. As a matter of fact, most issues right now are regarding contributing resources. I think this could be reduced by having clear guidance in the file.

Please let me know what you think about it.

[Thenlie]

If this is something deemed worthwhile, I would be happy to make it!

Here is a gist I made for another project as a rough idea. I think this is example goes into more detail than is needed here. Just a handful of links to the official GitHub docs on PRs, Forks and Issues should be enough.

Feel free to give me a ping with any follow up!

[eshellman]

we could add a link to your gist

[Thenlie]

we could add a link to your gist

You are more than welcome to! Since it may not all apply to this repo, I would also be happy to make a new one.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity during last 60 days :sleeping:

It will be closed in 30 days if no further activity occurs. To unstale this issue, remove stale label or add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest.

Thank you for your patience :heart:

[github-actions[bot]]

This issue has been automatically closed because it has been inactive during the last 30 days since being marked as stale.

As author or maintainer, it can always be reopened if you see that carry on been useful.

Anyway, thank you for your interest in contribute :heart: