Added: Add warning that hax support is not provided and asking questions will likely result in issue automatically closed or even ban

agnostic-apollo · agnostic-apollo · commit 6409019a400f · 2021-08-21T02:55:13.000+05:00
diff --git a/termux-shared/src/main/java/com/termux/shared/termux/TermuxUtils.java b/termux-shared/src/main/java/com/termux/shared/termux/TermuxUtils.java
@@ -241,7 +241,7 @@ public static String getReportIssueMarkdownString(@NonNull final Context context
 
         markdownString.append("## Where To Report An Issue");
 
-        markdownString.append("\n\n").append(context.getString(R.string.msg_report_issue)).append("\n");
+        markdownString.append("\n\n").append(context.getString(R.string.msg_report_issue, TermuxConstants.TERMUX_WIKI_URL)).append("\n");
 
         markdownString.append("\n\n### Email\n");
         markdownString.append("\n").append(MarkdownUtils.getLinkMarkdownString(TermuxConstants.TERMUX_SUPPORT_EMAIL_URL, TermuxConstants.TERMUX_SUPPORT_EMAIL_MAILTO_URL)).append("  ");
diff --git a/termux-shared/src/main/res/values/strings.xml b/termux-shared/src/main/res/values/strings.xml
@@ -55,7 +55,7 @@
 
 
     <!-- TermuxUtils -->
-    <string name="msg_report_issue">If you want to report this issue, then copy its text from the options menu (3-dots on top right) and post an issue on one of the following links.\n\nIf you are posting a Termux app crash report, then please provide details on what you were doing that caused the crash and how to reproduce it, if possible.\n\nIf you are posting an issue on Github, then post it in the repository at which the report belongs at. Issues opened or emails sent with **(partial) screenshots** instead of copied text or a file of this report **will likely be automatically closed/deleted**. You may optionally remove any device specific info that you consider private or don\'t want to share or that is not relevant to the issue.</string>
+    <string name="msg_report_issue">If you want to report this issue, then copy its text from the options menu (3-dots on top right) and post an issue on one of the following links.\n\nIf you are posting a Termux app crash report, then please provide details on what you were doing that caused the crash and how to reproduce it, if possible.\n\nIf you are posting an issue on Github, then post it in the repository at which the report belongs at. Issues opened or emails sent with **(partial) screenshots** instead of copied text or a file of this report **will likely be automatically closed/deleted**. You may optionally remove any device specific info that you consider private or don\'t want to share or that is not relevant to the issue.\n\nWe do not provide support for any hacking related tools/scripts. Any questions asked about them over email, on github or other official termux community forums **will likely be automatically closed/deleted** and may even result in **temporary or permanent** ban. Check %1$s/wiki/Hacking for details.</string>
 
 
 

Original file line number	Diff line number	Diff line change
`@@ -55,7 +55,7 @@`
`55`	`55`
`56`	`56`
`57`	`57`	`<!-- TermuxUtils -->`
`58`		- <string name="msg_report_issue">If you want to report this issue, then copy its text from the options menu (3-dots on top right) and post an issue on one of the following links.\n\nIf you are posting a Termux app crash report, then please provide details on what you were doing that caused the crash and how to reproduce it, if possible.\n\nIf you are posting an issue on Github, then post it in the repository at which the report belongs at. Issues opened or emails sent with (partial) screenshots instead of copied text or a file of this report will likely be automatically closed/deleted. You may optionally remove any device specific info that you consider private or don\'t want to share or that is not relevant to the issue.</string>
	`58`	+ <string name="msg_report_issue">If you want to report this issue, then copy its text from the options menu (3-dots on top right) and post an issue on one of the following links.\n\nIf you are posting a Termux app crash report, then please provide details on what you were doing that caused the crash and how to reproduce it, if possible.\n\nIf you are posting an issue on Github, then post it in the repository at which the report belongs at. Issues opened or emails sent with (partial) screenshots instead of copied text or a file of this report will likely be automatically closed/deleted. You may optionally remove any device specific info that you consider private or don\'t want to share or that is not relevant to the issue.\n\nWe do not provide support for any hacking related tools/scripts. Any questions asked about them over email, on github or other official termux community forums will likely be automatically closed/deleted and may even result in temporary or permanent ban. Check %1$s/wiki/Hacking for details.</string>
`59`	`59`
`60`	`60`
`61`	`61`