Feature: Automatically log issues on GitHub

[Lamparter]

What feature or improvement do you think would benefit Files?

When you add an ID to a YAML marker in an issue template, e.g.:

  # Files Version
  - type: input
    id: files_version # <-- THIS
    attributes:
      label: Files Version

You can then generate a URI to auto fill that value.
Try it out at https://github.com/files-community/Files/issues/new?template=bug_report.yml&files_version=abc123!

The app should be able to launch a URI when an error occurs, or this generated link could appear in the log file.

Requirements

• Add id attribute to each field of issue template
• Write a helper to calculate the URL for a stack trace
• (automatically|prompt to) open the URL when Files crashes

Files Version

3.8.11.0

Windows Version

10.0.22631.4602

Comments

No response

[Josh65-2201]

If you send it using Files settings > About > Feedback it already does this

[Lamparter]

It fills in the version, yes, but not more information like crash details etc.
The point of this is that it takes that to the next level.

[yaira2]

Which details do you have in mind?

[Lamparter]

The log file could be uploaded, for example.

Log file

App encodes log file in uri

Log

Or, the app could try to "calculate" what happened, to attempt to fill out the steps to reproduce section

1. App loaded (1s)
2. App crashed while loading cloud drives

[yaira2]

The log file could be uploaded, for example.

This would be cool, however there are privacy concerns with automatically uploading files, particularly ones that may contain paths.

Or, the app could try to "calculate" what happened, to attempt to fill out the steps to reproduce section

I'd like to hear more details about this proposal.

[Lamparter]

This would be cool, however there are privacy concerns with automatically uploading files, particularly ones that may contain paths

I'm not sure it would be difficult to redact paths.
Also, it's not different from the current configuration. The issue would still require a small amount of user interaction and they would be encouraged to review the issue body

Or, the app could try to "calculate" what happened, to attempt to fill out the steps to reproduce section

The best way to start on this would be by logging the actions the user takes.

[yaira2]

The paths are often required to debug, but at least the user is in control of the file and can choose not to upload it.

[Lamparter]

The log file wouldn't be uploaded directly, instead it would be inside a details block the user could edit.

Log file

(Log file inserted here)

The paths are often required to debug

Surely the app could just do a regex replace of the user profile directory with %userprofile%?

[Josh65-2201]

There's also emails that come from cloud drive names that should be filtered if this is going to be done.

[Lamparter]

As I said, the file wouldn't be directly uploaded so the user could still edit it.
Also, the user would still need to review the issue before sending, so it wouldn't be different from the current process where the user uploads the log file and can optionally exclude sensitive data.

[yaira2]

As I said, the file wouldn't be directly uploaded so the user could still edit it.

This will cause manually opened issues to have the file uploaded in one way, while those opened via Files would be uploaded in a different way.

[Lamparter]

What's wrong with that?