|
2 | 2 |
|
3 | 3 | Please note that this project is released with a [Contributor Code of Conduct](CODE-OF-CONDUCT.md). By participating in this project you agree to abide by its terms.
|
4 | 4 |
|
5 |
| - |
6 | 5 | ## Table of Contents
|
7 | 6 |
|
8 | 7 | - [Adding to This List](#adding-to-this-list)
|
9 | 8 | - [Updating Your Pull Request](#updating-your-pull-request)
|
10 | 9 |
|
11 |
| - |
12 | 10 | ## Adding to This List
|
13 | 11 |
|
14 | 12 | Please ensure your pull request adheres to the following guidelines:
|
15 | 13 |
|
16 |
| -* Search open and closed PRs to avoid duplicate suggestions. |
17 |
| -* Specify why the presentation is a must-watch, e.g., what did you learn from it, how will this be of value to developers? |
18 |
| -* Use the following format: <pre>`[**Talk Title**](link): Presenter, Event` `Duration`</pre> |
19 |
| - - For multiple presenters use a serial comma as appropriate, e.g., Marcia, Jan, and Cindy. |
20 |
| - - Don't use an ampersand with the serial comma, e.g., Greg, Peter, & Bobby. |
21 |
| - - If the presentation is a screencast or playlist use `(screencast)` or `(playlist)` in lieu of `Event`. |
22 |
| - - The duration should be surrounded by backticks (`), e.g., `28:30`. |
23 |
| -* Use the correct title of the presentation (don't rely on the title uploaded to YouTube, Vimeo, et al.). |
24 |
| -* Use [title-case](https://titlecaseconverter.com/). |
25 |
| -* Add suggestions to the end of the appropriate year block; if re-ordering is needed project maintainer will make a final determination. |
| 14 | +- Search open and closed PRs to avoid duplicate suggestions. |
| 15 | +- Specify why the presentation is a must-watch, e.g., what did you learn from it, how will this be of value to developers? |
| 16 | +- Use the following format: <pre>`[**Talk Title**](link): Presenter, Event` `Duration`</pre> |
| 17 | + - For multiple presenters use a serial comma as appropriate, e.g., Marcia, Jan, and Cindy. |
| 18 | + - Don't use an ampersand with the serial comma, e.g., Greg, Peter, & Bobby. |
| 19 | + - If the presentation is a screencast or playlist use `(screencast)` or `(playlist)` in lieu of `Event`. |
| 20 | + - The duration should be surrounded by backticks (`), e.g., `28:30`. |
| 21 | +- Use the correct title of the presentation (don't rely on the title uploaded to YouTube, Vimeo, et al.). |
| 22 | +- Use [title-case](https://titlecaseconverter.com/). |
| 23 | +- Add suggestions to the end of the appropriate year block; if re-ordering is needed project maintainer will make a final determination. |
26 | 24 |
|
27 | 25 | Thank you for your suggestions!
|
28 | 26 |
|
29 |
| - |
30 | 27 | ## Updating Your Pull Request
|
31 | 28 |
|
32 |
| -Sometimes a maintainer will ask you to edit your pull request before it's included. This is normally due to spelling errors or because your PR didn't match the above guidelines guidelines. [This write-up](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) covers the different ways you can change a pull request |
| 29 | +Sometimes a maintainer will ask you to edit your pull request before it's included. This is normally due to spelling errors or because your PR didn't match the above guidelines. [This write-up](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) covers the different ways you can change a pull request |
0 commit comments