Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add 💂♂️ for adding PR and issue templates
See original GitHub issueHello @carloscuesta 😎!
- Emoji: 💂♂️
- Code:
:guardsman: - Description: This emoji should be used when adding issue or pull request templates
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Multiple issue and pull request templates
To add multiple issue templates to a repository create an ISSUE_TEMPLATE/ directory in your project root. Within that ISSUE_TEMPLATE/ directory ...
Read more >How to add shortcuts to template in Ribbon in Outlook?
Add shortcut to template in Ribbon by adding Choose Forms in QAT. Most of time, not only special text, you may send email...
Read more >Usage: Issue and Pull Request templates - Docs
Gitea supports adding templates to the main branch of the repository so that they can autopopulate the form when users are creating issues...
Read more >GitHub pull request template
The easiest way to add a pull request template to your repository is by adding a file called pull_request_template.md in the root of...
Read more >Is it possible to have/use multiple github issue templates on ...
These templates will then be added as Markdown files to the .github/ISSUE_TEMPLATE/ directory within your project root. You then can decide ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Also this emoji is really platform specific to GitHub, #452 so maybe we should not consider it
I see… 🤔 so we should avoid one time use emojis?
well, I think messing with this kind of templating is similar to the DX idea (I commented about it here: https://github.com/carloscuesta/gitmoji/issues/214#issuecomment-637510342), maybe we could close this issue and treat PR/Issue templating as a Developer experience emoji 🤔