Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command for adding crash report to issue description #685

Open
Marcono1234 opened this issue Jun 7, 2021 · 0 comments
Open

Command for adding crash report to issue description #685

Marcono1234 opened this issue Jun 7, 2021 · 0 comments
Labels
discussion needed enhancement New feature or request

Comments

@Marcono1234
Copy link
Contributor

The Problem

Once #627 has been merged there will be cases in which Arisa won't add a crash report snippet to the issue description, this includes:

  • Existing crash reports which have been attached before the module has been activated
  • Multiple crash reports have been attached by the reporter
  • Crash reports attached by users other than the reporter
  • The issue description already contains a crash report snippet

For these cases it would be useful to have a command for manually updating the description with the snippet from a crash report attachment. The format of the {code} block being added should use the same format as #627 to make sure Arisa recognizes it, and to get consistent results.

Possible Solution

Add a $ARISA_INCLUDE_CRASH <attachment-name> (or similar) command; the command should be usable by Helper+.
It should:

  • Check if an attachment with the specified name exists and verify that it is a Minecraft crash report
  • NOT check whether the description already contains a crash report snippet. Adding a snippet should be possible even if the description already contains one.
  • Use the same snippet format as Update description with crash #627
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion needed enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant