youtube-dl

Another place where youtube-dl lives on
git clone git://git.oshgnacknak.de/youtube-dl.git
Log | Files | Refs | README | LICENSE

PULL_REQUEST_TEMPLATE.md (1783B)


      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 - [ ] [Searched](https://github.com/ytdl-org/youtube-dl/search?q=is%3Apr&type=Issues) the bugtracker for similar pull requests
     11 - [ ] Read [adding new extractor tutorial](https://github.com/ytdl-org/youtube-dl#adding-support-for-a-new-site)
     12 - [ ] Read [youtube-dl coding conventions](https://github.com/ytdl-org/youtube-dl#youtube-dl-coding-conventions) and adjusted the code to meet them
     13 - [ ] Covered the code with tests (note that PRs without tests will be REJECTED)
     14 - [ ] Checked the code with [flake8](https://pypi.python.org/pypi/flake8)
     15 
     16 ### In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under [Unlicense](http://unlicense.org/). Check one of the following options:
     17 - [ ] I am the original author of this code and I am willing to release it under [Unlicense](http://unlicense.org/)
     18 - [ ] I am not the original author of this code but it is in public domain or released under [Unlicense](http://unlicense.org/) (provide reliable evidence)
     19 
     20 ### What is the purpose of your *pull request*?
     21 - [ ] Bug fix
     22 - [ ] Improvement
     23 - [ ] New extractor
     24 - [ ] New feature
     25 
     26 ---
     27 
     28 ### Description of your *pull request* and other information
     29 
     30 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.