projects / yt-dlp.git / blame
| Commit | Line | Data |
|---|---|---|
| 1f552340 S |
1 | ## Please follow the guide below |
| 2 | ||
| 3 | - You will be asked some questions, please read them **carefully** and answer honestly | |
| 4 | - Put an `x` into all the boxes [ ] relevant to your *pull request* (like that [x]) | |
| 5 | - Use *Preview* tab to see how your *pull request* will actually look like | |
| 6 | ||
| 7 | --- | |
| 8 | ||
| 9 | ### Before submitting a *pull request* make sure you have: | |
| 10 | - [ ] At least skimmed through [adding new extractor tutorial](https://github.com/rg3/youtube-dl#adding-support-for-a-new-site) and [youtube-dl coding conventions](https://github.com/rg3/youtube-dl#youtube-dl-coding-conventions) sections | |
| 11 | - [ ] [Searched](https://github.com/rg3/youtube-dl/search?q=is%3Apr&type=Issues) the bugtracker for similar pull requests | |
| 12 | ||
| 13 | ### What is the purpose of your *pull request*? | |
| 14 | - [ ] Bug fix | |
| 15 | - [ ] New extractor | |
| 16 | - [ ] New feature | |
| 17 | ||
| 18 | --- | |
| 19 | ||
| 20 | ### Description of your *pull request* and other information | |
| 21 | ||
| 22 | Explanation of your *pull request* in arbitrary form goes here. Please make sure the description explains the purpose and effect of your *pull request* and is worded well enough to be understood. Provide as much context and examples as possible. |