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

Replace ISSUE_TEMPLATE with Bug-Report form #36

Merged
merged 1 commit into from
Nov 30, 2021

Conversation

mmlb
Copy link
Contributor

@mmlb mmlb commented Oct 1, 2021

Description

Replace ISSUE_TEMPLATE.md with Bug-Report.yml form based template.

Why is this needed

PR #34 added a form based issue template which causes extra friction to use the old template. By adding this in we should now have 2 options. I think this form is also nicer to use than the markdown template version.

attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex. email@example.com
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need PII/email here? Can we just use GitHub aliases?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree.

attributes:
label: What happened?
placeholder: Tell us what you see!
value: "A bug happened!"
Copy link
Contributor

Choose a reason for hiding this comment

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

Since we're setting placeholder we can probably drop value.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is all mostly an adaptation of the form from https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms. I agree the placeholder and value seem redundant, I'm tempted to keep it for the moment just to see what it looks like. I wish there was a "preview" option somewhere.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually, nm. Looking at screenshot in the example it definitely seems redundant so I'll get rid of value.

attributes:
label: What did you expect to happen?
placeholder: Tell us what you wanted!
value: "No bug"
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comment on value

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍

id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com)
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we have a real COC we can link to?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

indeed, will fix

@mmlb mmlb force-pushed the issue-template-2-bug-report branch from 9b14dc7 to 73bd247 Compare October 5, 2021 19:20
Copy link
Contributor Author

@mmlb mmlb left a comment

Choose a reason for hiding this comment

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

Thanks for the feedback @micahhausler ptal now

attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex. email@example.com
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree.

attributes:
label: What happened?
placeholder: Tell us what you see!
value: "A bug happened!"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is all mostly an adaptation of the form from https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms. I agree the placeholder and value seem redundant, I'm tempted to keep it for the moment just to see what it looks like. I wish there was a "preview" option somewhere.

id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

indeed, will fix

attributes:
label: What happened?
placeholder: Tell us what you see!
value: "A bug happened!"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually, nm. Looking at screenshot in the example it definitely seems redundant so I'll get rid of value.

attributes:
label: What did you expect to happen?
placeholder: Tell us what you wanted!
value: "No bug"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍

@micahhausler
Copy link
Contributor

LGTM

id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](./CODE_OF_CONDUCT.md)
Copy link
Contributor

@micahhausler micahhausler Oct 5, 2021

Choose a reason for hiding this comment

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

Can you absolute link to the COC in tinkerbell/org? I think this relative link won't work for other repos that get this template. (You might need to merge tinkerbell/org#6 first)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Merged and updated!

@mmlb mmlb force-pushed the issue-template-2-bug-report branch from 73bd247 to a039de4 Compare October 5, 2021 19:38
@mmlb mmlb requested a review from micahhausler October 5, 2021 19:38
@micahhausler
Copy link
Contributor

LGTM for real

micahhausler
micahhausler previously approved these changes Oct 5, 2021
@mmlb
Copy link
Contributor Author

mmlb commented Oct 5, 2021

apparently GH doesn't think much of your opinion ;). Need to get you write access to the repos first.

Signed-off-by: Manuel Mendez <mmendez@equinix.com>
@mmlb
Copy link
Contributor Author

mmlb commented Oct 5, 2021

Oops I just noticed that I used the wrong repo for the CoC link, fixed now.

@nshalman
Copy link
Member

@micahhausler want to review one more time?

@mmlb mmlb added the ready-to-merge Signal Mergify to merge the PR label Nov 30, 2021
@mmlb mmlb merged commit bd0f00d into tinkerbell:main Nov 30, 2021
@mmlb mmlb deleted the issue-template-2-bug-report branch November 30, 2021 19:56
@mmlb mmlb mentioned this pull request Dec 1, 2021
mmlb added a commit that referenced this pull request Dec 1, 2021
## Description

Add ISSUE_TEMPLATE/config.yaml

## Why is this needed

When #36 was merged the old markdown based issue template was removed but github doesn't use the Bug Report template. Maybe because the config.yaml is missing? Lets find out.
mmlb added a commit that referenced this pull request Dec 1, 2021
## Description

Reverts #36 which dropped ISSUE_TEMPLATE.md in favor of the fancy new issue forms.

## Why is this needed

GitHub isn't showing the fancy web form and I don't really have the time to debug it at the moment.'
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Signal Mergify to merge the PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants