You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the issue-reporting functionality is pretty barebones. It only allows using the generic template and adding more table rows to the metadata table. There are a few reasons to allow more customization: personal preference, adding more blocks, conforming to existing repo issue templates, supporting other forges/bugtrackers.
My use case for this is: I want to add a section to the issue report called "Additional Information" that suggests (in a comment) to add the file with TRACE-level logs, that are already written by default to a tmpfile.
I can contribute a patch, but I just want to make sure we're all on the same page on what's the better solution moving forward :)
A few options I see are (non-exclusive):
Make struct body public and let users just specify it themselves
Add more knobs to configure the structure
Add the knobs to tweak the URL building
Natively suggest using Markdown for body using types
Nuke most of the existing functionality and let users specify issue reporting as custom hook/POST request?
The text was updated successfully, but these errors were encountered:
Currently, the issue-reporting functionality is pretty barebones. It only allows using the generic template and adding more table rows to the
metadata
table. There are a few reasons to allow more customization: personal preference, adding more blocks, conforming to existing repo issue templates, supporting other forges/bugtrackers.My use case for this is: I want to add a section to the issue report called "Additional Information" that suggests (in a comment) to add the file with TRACE-level logs, that are already written by default to a tmpfile.
I can contribute a patch, but I just want to make sure we're all on the same page on what's the better solution moving forward :)
A few options I see are (non-exclusive):
body
public and let users just specify it themselvesThe text was updated successfully, but these errors were encountered: