Skip to content

Rename bug report template #3410

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

Merged
merged 1 commit into from
Mar 10, 2021
Merged

Rename bug report template #3410

merged 1 commit into from
Mar 10, 2021

Conversation

gtsiolis
Copy link
Contributor

@gtsiolis gtsiolis commented Mar 10, 2021

Follow up from #3405 (comment).

@gtsiolis gtsiolis force-pushed the gt/rename-bug-report-template branch from c9f5af5 to 5e77ebd Compare March 10, 2021 11:19
@gtsiolis gtsiolis changed the title Rename but report template Rename bug report template Mar 10, 2021
@gtsiolis
Copy link
Contributor Author

gtsiolis commented Mar 10, 2021

@csweichel could you review and merge this to try this one more time? 🏓

@gtsiolis gtsiolis requested a review from csweichel March 10, 2021 11:23
Copy link
Contributor

@csweichel csweichel left a comment

Choose a reason for hiding this comment

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

LGTM

@csweichel csweichel merged commit 14c1443 into main Mar 10, 2021
@csweichel csweichel deleted the gt/rename-bug-report-template branch March 10, 2021 13:23
@lukehefson
Copy link

lukehefson commented Apr 20, 2021

Hey 👋

I'm a product manager at GitHub working on issue forms. Just wanted to give you a quick heads up that issue_body is getting deprecated later today and I can see that you have a warning displayed for it here: https://github.com/gitpod-io/gitpod/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml

For more info see: https://github.com/gh-community/issue-forms-feedback/discussions/75#discussioncomment-576035 (let me know if you need an invite to that private feedback repo)

@gtsiolis
Copy link
Contributor Author

Thanks for heads-up @lukehefson! I've added #4017 to update this but I'm seeing the following error. Expected?

There is a problem with this template
Name must be unique.

@lukehefson
Copy link

but I'm seeing the following error. Expected?

There is a problem with this template
Name must be unique.

Ah yes. That's an issue with name conflicts on branch previews that we're looking into on our end. It shouldn't affect the form once merged.

@gtsiolis
Copy link
Contributor Author

Great, thanks for verifying @lukehefson!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants