chore: github issue template #1037
Conversation
crazy-max
force-pushed
the
bug-template
branch
2 times, most recently
from
4ccdeb4
to
1cb4391
Compare
|
Let's definitely get this in asap 🎉 - should save a lot of time going back and forth on getting reproduction details! |
crazy-max
force-pushed
the
bug-template
branch
from
efd184f
to
1aa645a
Compare
|
Also added "Feature request" and custom template for "Security and Vulnerabilities report" and "Questions and Discussions": https://github.com/crazy-max/buildx/issues/new/choose
|
crazy-max
force-pushed
the
bug-template
branch
from
1aa645a
to
58a5888
Compare
| label: I've found a bug and checked that ... | ||
| description: | | ||
| Make sure that your request fulfills all of the following requirements. | ||
| If one requirement cannot be satisfied, explain in detail why. | ||
| options: | ||
| - label: ... the documentation does not mention anything about my problem | ||
| - label: ... there are no open or closed issues that are related to my problem |
There was a problem hiding this comment.
This reads a little weird to me with the little paragraph in between:
Not a blocker, but also not sure how to rephrase this to flow a little easier.
| @@ -0,0 +1,9 @@ | |||
| # https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser | |||
There was a problem hiding this comment.
So had another thought here 😄
I wonder if we should have a little section here about Dockerfile-specific issues, where we link to the buildkit new issues page 🤔
There was a problem hiding this comment.
Hum not sure how to phrase this, let's see in a follow-up but that sounds like a good idea.
crazy-max
force-pushed
the
bug-template
branch
from
58a5888
to
60bdca3
Compare
crazy-max
force-pushed
the
bug-template
branch
2 times, most recently
from
8f57d4a
to
3d4d8ab
Compare
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
bug-template
branch
from
3d4d8ab
to
c0a9274
Compare
| **Please _DO NOT_ file a public issue**, instead send your report privately to | ||
| [security@docker.com](mailto:security@docker.com). | ||
|
|
||
| Security reports are greatly appreciated, and we will publicly thank you for it. |
There was a problem hiding this comment.
Not a blocker (we need to update in moby as well), but we should mention that we publicly thank them if they want to (some people may not want to, or their employer may not allow them to be mentioned)
adds a bug report issue forms template.
will look like this:
Signed-off-by: CrazyMax crazy-max@users.noreply.github.com