chore(website): update report as issue to use new issue forms #4916
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR, @armano2! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
bradzacher
reviewed
May 12, 2022
JoshuaKGoldberg
approved these changes
May 23, 2022
bradzacher
added a commit
that referenced
this pull request
May 31, 2022
I was wrong [when I originally told armano to remove these](#4916 (comment)). It appears that GH uses the issue form config to power the initial link from the issue chooser, and then completely ignores the config after that 😢 So without this param, the issue is filled without any tags at all!!!
bradzacher
added a commit
that referenced
this pull request
Jun 1, 2022
* chore(website): include labels in the report-an-issue button I was wrong [when I originally told armano to remove these](#4916 (comment)). It appears that GH uses the issue form config to power the initial link from the issue chooser, and then completely ignores the config after that 😢 So without this param, the issue is filled without any tags at all!!! * Update packages/website/src/components/lib/markdown.ts Co-authored-by: Armano <armano2@users.noreply.github.com> Co-authored-by: Armano <armano2@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Overview