devspace / awesome-github-templates

:octocat: Curated list of GitHub Issues and Pull Requests templates

DevSpace

Stay up to date with what's happening now on GitHub

Setup

1. Install the local dependencies

npm install

2. Compile, start local server, and watch for changes

gulp

The local server will be available at http://localhost:9000

License

MIT License © Zeno Rocha

awesome-github-templates's Issues

DOC: Growcss repo link is broken

https://github.com/growcss/growcss/blob/develop/.github/ISSUE_TEMPLATE.md linked as an example is no longer valid or has been moved.

Great project btw. Thanks for compiling examples!

Tell issue creators to use Speed OSS to add reward to Github Issues!

Add this text to ISSUE_TEMPLATE.md:

ADD A REWARD using [Speed](speedoss.com) to SOLVE this issue QUICKLY and SUPPORT this project.

Validate Links

Hey @zenorocha cool new project!

I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request or a commit is pushed to awesome-github-templates.

If you ran the tool, you would see that there is a link that redirects

 1. 301 http://github.com/zenorocha → https://github.com/zenorocha

Anyway, it is currently being used by many projects including

• https://github.com/vinta/awesome-python
• https://github.com/enaqx/awesome-react
• https://github.com/vsouza/awesome-ios
• https://github.com/caesar0301/awesome-public-datasets
• https://github.com/veggiemonk/awesome-docker

Examples

• https://travis-ci.org/vinta/awesome-python/builds/98201707 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/vsouza/awesome-ios/builds/106914621 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment or close if this is not right for you 😄

Tip for organization

Hi @zenorocha,
I know it's not mandatory, but it would not better use the files of template pull_request_template.md and issue_template.md within the folder .github? 🚀

Why are these awesome?

I'm not sure what makes any of the items here awesome. What is an awesome github issue template?

jj

uu

Template links should perhaps point to a specific commit, not a branch head?

Linking to branch heads means that if the target projects update their templates, the documents linked to from here will also change.

Depending on the intent of the curators, linking to versions at specific commits would avoid this.

Broken links for Find more [name]_TEMPLATE.md files

Hello!
Creating an issue here because I don't know what would be the most appropriate way to reach out. Hope this ends up being the correct channel and I don't end up imposing.

I believe both links for Find more ISSUE_TEMPLATE.md files and Find more PULL_REQUEST_TEMPLATE.md files are broken:

Right now they are respectively:
https://github.com/search?utf8=%E2%9C%93&q=in%3Apath+issue_template.md&type=Code&ref=searchresults
https://github.com/search?utf8=%E2%9C%93&q=in%3Apath+pull_request_template.md&type=Code&ref=searchresults

And I believe removing the in%3A and starting with pathin%3A fixes this, like so:
https://github.com/search?utf8=%E2%9C%93&q=path%3Aissue_template.md&type=Code&ref=searchresults
https://github.com/search?utf8=%E2%9C%93&q=path%3Apull_request_template.md&type=Code&ref=searchresults

Or, for exact file name matches (don't know which one makes more sense, probably the more permissive one) the below regex can be used:
path:/(^|\/)issue_template.md\.md$/
path:/(^|\/)pull_request_template\.md$/