-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Centralize issues/github templates and CONTRIBUTING.md #215
Comments
I agree 👍 I had the same thoughts. Moreover, I think we also should unify a labels for all repos 😄 |
Same thought here too about labels ;) I am looking into mergify config right now (after drinking coffee with java beans) |
@ihostage So mergify can not read configs from the |
@mkurz Yep, I explored Mergify opportunities too and know that he cannot do that 😞 |
@ihostage Please vote up this discussion as well: Mergifyio/mergify#2205 thanks! |
Probably a good idea to move most (all?) of them into the
.github
repo (we have there one already):Same with the issue an pull request templates:
For issues I think we should just use a
ISSUE_TEMPLATE
folder, we can influence sorting by numbering the files, e.g. see here.More information:
The text was updated successfully, but these errors were encountered: