Source identity
| Field | Recorded value |
|---|---|
| Source type | GitHub source |
| Original record | Janady13/awesome-nextjs / CONTRIBUTING.md |
| Date | Not specified in source |
| Repository | Janady13/awesome-nextjs |
| Revision | 048055be9bf85015a6d6f812c8d3b0686ae44bce |
| Branch | master |
| Path or archive member | CONTRIBUTING.md |
| Original SHA-256 | 9285d94440fec4d5c937286574f15e37b0bcb5272ad29ccf9cfd6e1a50073d9d |
| Git blob SHA | 02e3d885ff69c4adeaf84cacf6359b9db63416d0 |
| Reading-copy SHA-256 | 9285d94440fec4d5c937286574f15e37b0bcb5272ad29ccf9cfd6e1a50073d9d |
Recovered source transcript
Download complete source text ↓24 lines · 1.5 KB
# Contribution Guidelines
Ensure your pull request adheres to the following guidelines:
- Search previous suggestions before making a new one, as yours may be a duplicate.
- Make an individual pull request for each suggestion.
- Use [title-casing](http://titlecapitalization.com) (AP style).
- Use the following format: `[Title Case Name](link) - Description.`
> :information_source: [Articles](https://github.com/unicodeveloper/awesome-nextjs#articles) should use the `[Title Case Name](link)` format.
- Keep descriptions short and simple, but descriptive.
- Start the description with a capital and end with a full stop/period.
> :information_source: You can use an emoji, only before the Title-Cased Description.
- Check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.
- New categories or improvements to the existing categorization are welcome.
- Pull requests should have a useful title.
- The body of your commit message should contain a link to the repository.
Thank you for your suggestion!
### Updating your PR
A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. There's no need to open a new PR, just edit the existing one. If you're not sure how to do that, [here is a guide](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) on the different ways you can update your PR so that we can merge it.