[Feature] Add Repository-Level Triage Rules Configuration

[anshul23102]

Summary

Triage behavior is the same for all repositories. A configuration system would let maintainers define repo-specific rules: ignore certain label combinations, auto-close criteria, custom priority keywords.

Proposed Solution

Support a .isscope.yml file in the repository root:

version: 1

priority:
  critical_keywords: ["crash", "data loss", "security", "CVE"]
  ignore_labels: ["wontfix", "duplicate"]

auto_close:
  conditions:
    - type: "question"
      without_response_days: 14

labels:
  map:
    type:bug: "bug"
    type:feature: "enhancement"

exclusions:
  authors: ["dependabot[bot]", "renovate[bot]"]
  title_patterns: ["^chore:", "^docs:"]

When isscope loads a repository, it checks for .isscope.yml and merges the file's settings with the defaults. Issues matching exclusions criteria are skipped silently.

Acceptance Criteria

• .isscope.yml in the root is loaded and applied for that repository.
• Custom critical_keywords elevate matching issues to critical priority.
• Issues from excluded authors are not triaged.
• Label mapping translates isscope internal labels to repository-specific label names.
• Missing or invalid config fields fall back to defaults with a warning shown to the user.
• Config is cached for the session; a "Reload config" button bypasses the cache.

[anshul23102]

Hi @vee1e, I'd like to work on this. Plan: add a per-repository config file (e.g. .isscope.yml) allowing custom triage rules/label mappings to override the global defaults on a per-repo basis. Requesting assignment under GSSoC 2026.

/assign
/claim