Make a bug report guideline to guide new github users #5320
Replies: 3 comments
-
Update : I found a way to include all of the form data in a single Github URL : This can be clicked by the user and he does not have to fill out the crash report by himself. |
Beta Was this translation helpful? Give feedback.
-
Hi @Oxey405 ! A quick explanation about the bug reporting (from a technical point of view):
So far, I personally did not thought about how to increase or improve the data that we gather about the crash. So maybe there's something here to improve. Regarding the issue that is "How to make the user send context about the crash", this is quite complexe since it's related to human behavior:
Considering this situation, we can consider that we end up having 1 issue opened on GitHub for something like 10 crashes. Or is it 100? 1000? It's hard to know. I don't think we send analytics about that. So we can add a form to fill out when a crash happens but it's very likely that we would see far less crash reports. Maybe we could create an incentive to create beautiful crash reports with detailed context but I lack ideas about how to achieve that. What do you think? |
Beta Was this translation helpful? Give feedback.
-
Hey @AlexandreSi I thought a bit more about it ; What do you think ? |
Beta Was this translation helpful? Give feedback.
-
The problem
Hello !
Throughout my browsing of the issues in GDevelop, I noticed a recurrent problem in the issues about crash reports.
The problem is that, most users don't even fill out the form and just send the crash report as it's nothing and never answer back to contributor's questions.
Suggested solution :
Make a in-editor bug report form that sends all of the crash report data to a github action which rewrite all infos to a github issue.
Also make a clear (if it does not already exists) crash report guideline for everyone translated in as many languages as possible through crowdin.
To be clear, I am not putting the blame on new users but more on the fact that it's not practical for inexperimented users to understand github.
I'm willing to make a PR for a new in-IDE screen form for that but for the "post it to github" part, I'm not quite sure how to do it because I don't have direct access to GDevelop's repo.
Beta Was this translation helpful? Give feedback.
All reactions