-
Probably a good idea to move most (all?) of them into the `.github` repo ([we have there one already](https://github.com/playframework/.github/blob/main/CONTRIBUTING.md)):
* https://github.com/play…
mkurz updated
2 years ago
-
Hi everyone!
Just a quick heads-up here.
Since we've introduced the issue template, issues get solved way faster than before.
The last weeks we've noticed a decline in the usage in which us…
-
Currently any new user who raises a new issue or PR is not following proper guidelines to raise an issue or a PR for the repository.
We should have an **issue template** and **PR template** that ar…
-
```
After clicking ok on the message "Could not recognize component type LineIC" I
get an empty templates frame, is also an old issue never filed. What's
happening here?
What version of the product…
-
```
After clicking ok on the message "Could not recognize component type LineIC" I
get an empty templates frame, is also an old issue never filed. What's
happening here?
What version of the product…
-
```
After clicking ok on the message "Could not recognize component type LineIC" I
get an empty templates frame, is also an old issue never filed. What's
happening here?
What version of the product…
-
```
After clicking ok on the message "Could not recognize component type LineIC" I
get an empty templates frame, is also an old issue never filed. What's
happening here?
What version of the product…
-
[GitHub Issue Templates](https://github.com/blog/2111-issue-and-pull-request-templates) are great, but they are somewhat misnamed: you can't have multiple templates, but only a single template which a…
-
I'm starting this issue as a place to discuss
- first, whether or not we should implement templates for GitHub Issues and PRs
- and if so, what should be included in those templates.
IMO, I think…
-
*How better?* I don't know!
Currently this issue contains only what *I think* could be useful, this needs more discussion but there are plenty things we could improve in our templates.
New templ…