Skip to content
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

Proposal: Introduce new issue template for native executable bugs #36492

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

zakkak
Copy link
Contributor

@zakkak zakkak commented Oct 16, 2023

The aim of this is to prompt the reported to make sure the issue is native-image specific and also remove the GraalVM field from issue reports not using GraalVM.

@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label Oct 16, 2023
@zakkak zakkak changed the title Introduce new issue template for native executable bugs Proposal: Introduce new issue template for native executable bugs Oct 16, 2023
@@ -0,0 +1,77 @@
name: Bug Report for Quarkus native executables
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check in a personal project if we can order templates by changing the name of the YAML file? Because if this gets not just below Bug report, I think people won't see it at all.

If adjusting the YAML file name with 1_..., 2_... works, we should probably do that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, I kept the name start to be "Bug Report" to preserve alphabetical order, but the order is based on the yaml file name not the name template name.

Renaming the yaml file seems to do the trick:

image

@zakkak zakkak force-pushed the 2023-10-16-native-issue-template branch from e217660 to 494f483 Compare October 16, 2023 09:24
@gsmet
Copy link
Member

gsmet commented Oct 16, 2023

That works too :).

@zakkak zakkak added the area/housekeeping Issue type for generalized tasks not related to bugs or enhancements label Oct 16, 2023
@zakkak zakkak force-pushed the 2023-10-16-native-issue-template branch from 494f483 to 36242a2 Compare October 16, 2023 11:17
The aim of this is to prompt the reported to make sure the issue is
native-image specific and also remove the GraalVM field from issue
reports not using GraalVM.
@zakkak zakkak force-pushed the 2023-10-16-native-issue-template branch from 36242a2 to 6e8f2ee Compare October 17, 2023 05:54
@gsmet gsmet added the area/infra internal and infrastructure related issues label Oct 18, 2023
@gsmet gsmet merged commit 89ed09e into quarkusio:main Oct 18, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/housekeeping Issue type for generalized tasks not related to bugs or enhancements area/infra internal and infrastructure related issues area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants