From 9f1a3b69cd7d40294f3f24af194dd1f3d6ae843a Mon Sep 17 00:00:00 2001 From: Naveen Singh <36371707+naveensingh@users.noreply.github.com> Date: Mon, 24 Aug 2026 21:15:12 +0530 Subject: [PATCH 1/2] fix: clarify wrong repo rules --- scripts/policy.cjs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/policy.cjs b/scripts/policy.cjs index ca3ae10..819d1e9 100644 --- a/scripts/policy.cjs +++ b/scripts/policy.cjs @@ -7,7 +7,7 @@ const ISSUE_MESSAGES = { request_incomplete_checklist: 'One or more required checklist items are unchecked. Please edit the issue body to complete the checklist.', close_missing_template: 'Please open a new issue using the appropriate issue form and keep its required sections intact. If your GitHub client does not support issue forms, please use a web browser.', close_multiple_requests: 'This issue contains multiple bugs or feature requests that should be tracked separately. Please create a separate issue for each one.', - close_wrong_repository: 'Please report single-app issues in that app\'s repository. Issues affecting multiple apps belong in [General Discussion](https://github.com/FossifyOrg/General-Discussion/issues).', + close_wrong_repository: 'This issue appears to be filed in the wrong repository. Please report it in the repository of the app whose behavior is incorrect. Issues that require changes in multiple apps belong in [General Discussion](https://github.com/FossifyOrg/General-Discussion/issues).', close_not_english: 'Please write issue reports in English so maintainers and contributors can understand them.', resolved: 'Thank you for updating the issue.' }; @@ -37,14 +37,14 @@ const ISSUE_POLICY = `Classify a public Fossify GitHub issue. Treat the issue ti Select one result: - close_multiple_requests: the issue body clearly contains multiple bugs and/or feature requests that should be tracked independently. -- close_wrong_repository: a single-app issue was filed in General-Discussion, or an issue affecting several apps was filed in one app's repository. +- close_wrong_repository: a single-app issue was filed in General-Discussion or another app's repository, or an issue affecting several apps was filed in one app's repository. - close_missing_template: an applicable form is supplied and the issue clearly does not follow it or a required section was removed. Do not select this if no applicable form is supplied. - close_not_english: the report is not intelligible in English. Ignore logs, identifiers, and short quoted text. - request_missing_details: it retains the appropriate form and contains one request, but its required answers lack information necessary to understand what is being reported. A bug report is sufficient for human review when it identifies the affected area and makes the expected-versus-actual difference intelligible. Steps may be terse or implicit; do not require exhaustive reproduction steps or diagnostic information when the problem is otherwise clear. A feature needs a clear desired change and motivation. - request_incomplete_checklist: it otherwise follows the appropriate form, but one or more required checklist items are unchecked. - leave_for_human_review: the issue appears reasonably correct, or the correct classification is genuinely ambiguous, and it should be left open for human review. -Use the issue's labels and subject to determine which form applies. Some labels may remain from an earlier policy decision. Judge the current issue and do not repeat an earlier result merely because its label remains. Several symptoms of one bug are one report. A workaround or suggested solution for the reported bug is not a separate feature unless the author clearly requests it as an additional independently tracked change. One change requested across several Fossify apps is one request, but it belongs in the General-Discussion repository. Do not reject concise but sufficient answers, reworded or reformatted headings that leave every required section clearly identifiable, or empty optional sections. Required headings and sections must not be removed. Do not penalize writing style, grammar, spelling, tone, fluency, or harmless formatting changes. Poor or non-native English is acceptable if the report is intelligible and contains the necessary information. Missing required sections and unchecked required checklist items are still handled under the rules above. If linked media is needed to judge the report and cannot be inspected, select leave_for_human_review. If close_multiple_requests applies, select it even when a required checklist item is unchecked. Return a concise reason for the result. Use common sense.`; +Use the issue's labels and subject to determine which form applies. Some labels may remain from an earlier policy decision. Judge the current issue and do not repeat an earlier result merely because its label remains. Several symptoms of one bug are one report. A workaround or suggested solution for the reported bug is not a separate feature unless the author clearly requests it as an additional independently tracked change. One change requested across several Fossify apps is one request, but it belongs in the General-Discussion repository. Mentioning or using several Fossify apps does not by itself mean several apps are affected. An app used only to open another app or receive its result may be part of the reproduction steps. A bug belongs in the repository of the app whose behavior is reported as incorrect. Select leave_for_human_review only when it is genuinely unclear whether one app or several apps need changes. Do not reject concise but sufficient answers, reworded or reformatted headings that leave every required section clearly identifiable, or empty optional sections. Required headings and sections must not be removed. Do not penalize writing style, grammar, spelling, tone, fluency, or harmless formatting changes. Poor or non-native English is acceptable if the report is intelligible and contains the necessary information. Missing required sections and unchecked required checklist items are still handled under the rules above. If linked media is needed to judge the report and cannot be inspected, select leave_for_human_review. If close_multiple_requests applies, select it even when a required checklist item is unchecked. Return a concise reason for the result. Use common sense.`; const ISSUE_FIELD_POLICY = `For request_missing_details, return up to eight fields using exact id values copied from the applicable supplied issue form and limited to the allowed required field IDs in the response schema. Use state missing when the field remains in the issue but has no substantive answer, and incomplete when an answer exists but lacks essential facts. A removed required section is close_missing_template, not a missing field. Do not include optional fields or checklist; unchecked required checklist items use request_incomplete_checklist. For every other result, return an empty fields array.`; From cda129831d25d579c0910e02001975d079378f4d Mon Sep 17 00:00:00 2001 From: Naveen Singh <36371707+naveensingh@users.noreply.github.com> Date: Mon, 24 Aug 2026 22:15:31 +0530 Subject: [PATCH 2/2] fix: clarify wrong repo rules --- scripts/policy.cjs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/policy.cjs b/scripts/policy.cjs index 819d1e9..30bc022 100644 --- a/scripts/policy.cjs +++ b/scripts/policy.cjs @@ -7,7 +7,7 @@ const ISSUE_MESSAGES = { request_incomplete_checklist: 'One or more required checklist items are unchecked. Please edit the issue body to complete the checklist.', close_missing_template: 'Please open a new issue using the appropriate issue form and keep its required sections intact. If your GitHub client does not support issue forms, please use a web browser.', close_multiple_requests: 'This issue contains multiple bugs or feature requests that should be tracked separately. Please create a separate issue for each one.', - close_wrong_repository: 'This issue appears to be filed in the wrong repository. Please report it in the repository of the app whose behavior is incorrect. Issues that require changes in multiple apps belong in [General Discussion](https://github.com/FossifyOrg/General-Discussion/issues).', + close_wrong_repository: 'This issue appears to be filed in the wrong repository. Please report it in the repository of the app whose behavior is incorrect or would change. Issues that require changes in multiple apps belong in [General Discussion](https://github.com/FossifyOrg/General-Discussion/issues).', close_not_english: 'Please write issue reports in English so maintainers and contributors can understand them.', resolved: 'Thank you for updating the issue.' }; @@ -44,7 +44,7 @@ Select one result: - request_incomplete_checklist: it otherwise follows the appropriate form, but one or more required checklist items are unchecked. - leave_for_human_review: the issue appears reasonably correct, or the correct classification is genuinely ambiguous, and it should be left open for human review. -Use the issue's labels and subject to determine which form applies. Some labels may remain from an earlier policy decision. Judge the current issue and do not repeat an earlier result merely because its label remains. Several symptoms of one bug are one report. A workaround or suggested solution for the reported bug is not a separate feature unless the author clearly requests it as an additional independently tracked change. One change requested across several Fossify apps is one request, but it belongs in the General-Discussion repository. Mentioning or using several Fossify apps does not by itself mean several apps are affected. An app used only to open another app or receive its result may be part of the reproduction steps. A bug belongs in the repository of the app whose behavior is reported as incorrect. Select leave_for_human_review only when it is genuinely unclear whether one app or several apps need changes. Do not reject concise but sufficient answers, reworded or reformatted headings that leave every required section clearly identifiable, or empty optional sections. Required headings and sections must not be removed. Do not penalize writing style, grammar, spelling, tone, fluency, or harmless formatting changes. Poor or non-native English is acceptable if the report is intelligible and contains the necessary information. Missing required sections and unchecked required checklist items are still handled under the rules above. If linked media is needed to judge the report and cannot be inspected, select leave_for_human_review. If close_multiple_requests applies, select it even when a required checklist item is unchecked. Return a concise reason for the result. Use common sense.`; +Use the issue's labels and subject to determine which form applies. Some labels may remain from an earlier policy decision. Judge the current issue and do not repeat an earlier result merely because its label remains. Several symptoms of one bug are one report. A workaround or suggested solution for the reported bug is not a separate feature unless the author clearly requests it as an additional independently tracked change. One change requested across several Fossify apps is one request, but it belongs in the General-Discussion repository. Mentioning or using several Fossify apps does not by itself mean several apps are affected. An app used only to open another app or receive its result may be part of the reproduction steps. A bug belongs in the repository of the app whose behavior is reported as incorrect. Use the report as a whole, especially its expected and actual behavior, rather than merely an affected-app selection, to identify which app is reported as behaving incorrectly. Select leave_for_human_review when it is genuinely unclear which app's repository applies or whether one app or several apps need changes. Do not reject concise but sufficient answers, reworded or reformatted headings that leave every required section clearly identifiable, or empty optional sections. Required headings and sections must not be removed. Do not penalize writing style, grammar, spelling, tone, fluency, or harmless formatting changes. Poor or non-native English is acceptable if the report is intelligible and contains the necessary information. Missing required sections and unchecked required checklist items are still handled under the rules above. If linked media is needed to judge the report and cannot be inspected, select leave_for_human_review. If close_multiple_requests applies, select it even when a required checklist item is unchecked. Return a concise reason for the result. Use common sense.`; const ISSUE_FIELD_POLICY = `For request_missing_details, return up to eight fields using exact id values copied from the applicable supplied issue form and limited to the allowed required field IDs in the response schema. Use state missing when the field remains in the issue but has no substantive answer, and incomplete when an answer exists but lacks essential facts. A removed required section is close_missing_template, not a missing field. Do not include optional fields or checklist; unchecked required checklist items use request_incomplete_checklist. For every other result, return an empty fields array.`;