fix: prefill the report form's title instead of its fields - #17
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Category
Bugfix
Overview
The Report links on device pages open a blank issue editor instead of the form. The bare form link renders fine, it's the
&device=tegu&rom=...prefill that tips it over, so every Report link on the site has been dead. Now the link only prefills the title, like[Report]: Google Pixel 9a (tegu) on LineageOS, and you copy the device and ROM across yourself.I haven't worked out why GitHub drops the form when a field is prefilled. Nothing in the template looks off and the bot only reads the body, so this sidesteps it rather than fixing the cause. I also haven't seen the new link render while signed in yet.
Issue Number
None