Introduce issue forms and update debug output for forms#2160
Introduce issue forms and update debug output for forms#2160polarathene merged 31 commits intomasterfrom
Conversation
|
I cancelled the first |
Co-authored-by: William Desportes <[email protected]>
|
I will review carefully later today |
wernerfred
left a comment
There was a problem hiding this comment.
Thanks for this inital block of work. All in all this seems fine. But imho the wording is a bit to "agressive". I know that we have to deal a lot with people who don't use the templates or don't provide enough information but this form is here to solve this problem :)
As we do not want to kind of "scare" a few people from filing issue reports i vote for a friendlier wording here and there.
Co-authored-by: Frederic Werner <[email protected]>
10 days no response, requests were all addressed.
|
No rush to merge this right? I have dismissed @wernerfred stale review, but I think we can leave this open over the weekend in case he still wants to chime in. If no other activity merge from Monday? |
wernerfred
left a comment
There was a problem hiding this comment.
Sorry for not responding for a week now but i needed some time offline 🏞️
I looked at the rendering of the form and feel like that the <= syntax is not looking nice imho. I proposed a written variant but feel free to change the wording.
Thanks @polarathene for thinking of me and giving me time to throw in my two cents once again. 🚀
Feel free to merge if you disagree with my changes.
a5b6018
|
Aright. I incorporated @wernerfred's feedback and added a feedback text area field to the forms for users to tell us their impressions too. I hope that all is well now :) Please leave your reviews (for the last time I hope) again :D |
wernerfred
left a comment
There was a problem hiding this comment.
Nice idea with the feedback section 👍🏻
Description
This PR introduces GitHub forms and slightly alters the debug output for better visibility.
The debug output changed in so far as now a self-written function prints the environment in a useful way, and we do not use
printenvanymore, because I thinkprintenvclutters the whole log with information no one really needs. I did this because with the new form, we encourage people to useDMS_DEBUG=1more, so I figured prettier log output / a non-cluttered log to begin with would be nice.See this maintainers discussion
Type of change
Checklist:
docs/)