playframework / play-meta

Team management & cross-repository effort tracking
Apache License 2.0
8 stars 8 forks source link

Centralize issues/github templates and CONTRIBUTING.md #215

Open mkurz opened 2 years ago

mkurz commented 2 years ago

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:

ihostage commented 2 years ago

I agree 👍 I had the same thoughts. Moreover, I think we also should unify a labels for all repos 😄

mkurz commented 2 years ago

Same thought here too about labels ;) I am looking into mergify config right now (after drinking coffee with java beans)

mkurz commented 2 years ago

@ihostage So mergify can not read configs from the .github repo yet and also can not extend other configs :cry:. I opened a pull request to at least read configs from the .github repo: https://github.com/Mergifyio/mergify-engine/pull/4050 I did not implement _extends however (yet :wink:)

ihostage commented 2 years ago

@mkurz Yep, I explored Mergify opportunities too and know that he cannot do that 😞 And it's great that you tried to implement this 👍

mkurz commented 2 years ago

@ihostage Please vote up this discussion as well: https://github.com/Mergifyio/mergify-engine/discussions/2205 thanks!