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

Add issue forms #5490

Merged
merged 21 commits into from Jun 14, 2022
Merged

Add issue forms #5490

merged 21 commits into from Jun 14, 2022

Conversation

eddumelendez
Copy link
Member

Introducing issue forms for: bug report, enhacements and features.
In case of help or question there is a link to the slack channel.

Introducing issue forms for: bug report, enhacements and features.
In case of help or question there is a link to the slack channel.
@eddumelendez eddumelendez requested a review from a team as a code owner June 13, 2022 21:09
@eddumelendez
Copy link
Member Author

You can see a preview of those forms here

@kiview
Copy link
Member

kiview commented Jun 14, 2022

Wow, this is super cool, thanks for looking into this 🙌

I have one question regarding the intent of this selection field:
image

Yes means: I used the old version, updated to the new version, and the issue persists.
No means: I used the old version, updated to the new version, and the issue is solved.

Is it correct? Does this mainly act for nudging users into trying out with the latest version?

Copy link
Member

@kiview kiview left a comment

Choose a reason for hiding this comment

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

Some suggestions for different wording, accept as you see fit. Really excited to see the results of using these forms 🤗

.github/ISSUE_TEMPLATE/bug_report.yaml Outdated Show resolved Hide resolved
attributes:
label: Module
description: Which testcontainers module are you using?
options:
Copy link
Member

Choose a reason for hiding this comment

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

I think for now we can hardcode the modules, but eventually, we probably want to automate or semi-automate this.

.github/ISSUE_TEMPLATE/bug_report.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/feature.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/feature.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/feature.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/feature.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/feature.yaml Outdated Show resolved Hide resolved
@kiview kiview added this to the next milestone Jun 14, 2022
eddumelendez and others added 19 commits June 14, 2022 07:58
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
Co-authored-by: Kevin Wittek <kiview@users.noreply.github.com>
@eddumelendez
Copy link
Member Author

Yes means: I used the old version, updated to the new version, and the issue persists.
No means: I used the old version, updated to the new version, and the issue is solved.

Is it correct? Does this mainly act for nudging users into trying out with the latest version?

Yes, that's the meaning in the reply. Although, the main act is not updating to the latest but identify if the issue was already fixed in a later version (not necessarily latest one)

Copy link
Member

@bsideup bsideup left a comment

Choose a reason for hiding this comment

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

This is awesome! 💯

@eddumelendez eddumelendez merged commit b3f1b66 into master Jun 14, 2022
@delete-merged-branch delete-merged-branch bot deleted the issue_forms branch June 14, 2022 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants