From 24a3cb9e201990635e3431f4a6cb994202f7cb70 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 14:49:11 +0000 Subject: [PATCH 1/3] meta(issues): Redirect requests to the new CLI Co-Authored-By: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/01-feature.yml | 29 --------------------------- .github/ISSUE_TEMPLATE/02-bug.yml | 26 +++++++++++++++++++++++- 2 files changed, 25 insertions(+), 30 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/01-feature.yml diff --git a/.github/ISSUE_TEMPLATE/01-feature.yml b/.github/ISSUE_TEMPLATE/01-feature.yml deleted file mode 100644 index 767fe7ae2b..0000000000 --- a/.github/ISSUE_TEMPLATE/01-feature.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: 💡 Feature Request -description: Suggest an idea for improving Sentry CLI -labels: ["CLI", "Feature"] -body: - - type: textarea - id: problem - attributes: - label: Problem Statement - description: What problem could CLI solve that it currently doesn't? - placeholder: |- - I want to make whirled peas, but Sentry doesn't blend. - validations: - required: true - - - type: textarea - id: expected - attributes: - label: Solution Brainstorm - description: We know you have bright ideas to share ... share away, friend. - placeholder: |- - Add a blender to Sentry. - validations: - required: false - - - type: markdown - attributes: - value: |- - ## Thanks 🙏 - Check our [triage docs](https://open.sentry.io/triage/) for what to expect next. diff --git a/.github/ISSUE_TEMPLATE/02-bug.yml b/.github/ISSUE_TEMPLATE/02-bug.yml index 1f40d9dad4..be88a6ff11 100644 --- a/.github/ISSUE_TEMPLATE/02-bug.yml +++ b/.github/ISSUE_TEMPLATE/02-bug.yml @@ -1,7 +1,31 @@ name: 🐞 Bug Report -description: Report a bug in Sentry CLI +description: Report a bug that prevents migration to the new Sentry CLI labels: ["CLI", "Bug"] body: + - type: markdown + attributes: + value: | + > [!IMPORTANT] + > This legacy CLI is no longer under active development. Please try the [new Sentry CLI](https://cli.sentry.dev/) and report bugs in the [new CLI repository](https://github.com/getsentry/cli/issues/new) instead. + + Only open a bug here if migrating to the new CLI is impossible or infeasible for a concrete reason. Bug reports that do not explain a migration blocker will be closed. + + - type: textarea + id: migration-blocker + attributes: + label: Migration blocker + description: Why is migrating to the new Sentry CLI impossible or infeasible? Describe the concrete technical or operational blocker. A preference to keep using this legacy CLI is not sufficient. + placeholder: Include the new CLI command or workflow you tried, what prevents it from replacing your current sentry-cli workflow, and any constraints that rule out a workaround. + validations: + required: true + - type: checkboxes + id: migration-confirmation + attributes: + label: Migration blocker confirmation + options: + - label: I tried the new Sentry CLI and have described a concrete reason why migrating to it is impossible or infeasible. + required: true + - type: markdown attributes: value: | From 759f97945940d4d08edd853cff608460049367e5 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 14:53:33 +0000 Subject: [PATCH 2/3] meta(issues): Clarify legacy bug eligibility Co-Authored-By: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/02-bug.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/02-bug.yml b/.github/ISSUE_TEMPLATE/02-bug.yml index be88a6ff11..abd84b698b 100644 --- a/.github/ISSUE_TEMPLATE/02-bug.yml +++ b/.github/ISSUE_TEMPLATE/02-bug.yml @@ -1,5 +1,5 @@ name: 🐞 Bug Report -description: Report a bug that prevents migration to the new Sentry CLI +description: Report a bug in the legacy Sentry CLI labels: ["CLI", "Bug"] body: - type: markdown @@ -8,14 +8,14 @@ body: > [!IMPORTANT] > This legacy CLI is no longer under active development. Please try the [new Sentry CLI](https://cli.sentry.dev/) and report bugs in the [new CLI repository](https://github.com/getsentry/cli/issues/new) instead. - Only open a bug here if migrating to the new CLI is impossible or infeasible for a concrete reason. Bug reports that do not explain a migration blocker will be closed. + This form is for bugs in the legacy `sentry-cli`. We will only consider a bug report here if you also have a concrete reason why using the new CLI is impossible or infeasible. That reason is separate from the legacy CLI bug you are reporting below. - type: textarea id: migration-blocker attributes: - label: Migration blocker - description: Why is migrating to the new Sentry CLI impossible or infeasible? Describe the concrete technical or operational blocker. A preference to keep using this legacy CLI is not sufficient. - placeholder: Include the new CLI command or workflow you tried, what prevents it from replacing your current sentry-cli workflow, and any constraints that rule out a workaround. + label: Reason you cannot use the new Sentry CLI + description: Describe the concrete technical or operational situation that makes the new CLI impossible or infeasible for you. This does not need to be a bug in either CLI, but it must be independent of the legacy CLI bug reported below. A preference to keep using the legacy CLI is not sufficient. + placeholder: Describe the new CLI capability, compatibility requirement, environment constraint, or other blocker that prevents migration. validations: required: true - type: checkboxes @@ -23,7 +23,7 @@ body: attributes: label: Migration blocker confirmation options: - - label: I tried the new Sentry CLI and have described a concrete reason why migrating to it is impossible or infeasible. + - label: I have described a concrete reason, separate from the bug below, why I cannot use the new Sentry CLI instead. required: true - type: markdown From 87251659b023ca2025d7dd54d720027c17eb0c18 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 15:00:18 +0000 Subject: [PATCH 3/3] meta(issues): Guide reporters through CLI migration Co-Authored-By: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/02-bug.yml | 32 ++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/02-bug.yml b/.github/ISSUE_TEMPLATE/02-bug.yml index abd84b698b..7652b7aeda 100644 --- a/.github/ISSUE_TEMPLATE/02-bug.yml +++ b/.github/ISSUE_TEMPLATE/02-bug.yml @@ -5,26 +5,32 @@ body: - type: markdown attributes: value: | - > [!IMPORTANT] - > This legacy CLI is no longer under active development. Please try the [new Sentry CLI](https://cli.sentry.dev/) and report bugs in the [new CLI repository](https://github.com/getsentry/cli/issues/new) instead. + Thanks for taking the time to report a bug! Before you continue, please try the [new Sentry CLI](https://cli.sentry.dev/). This legacy `sentry-cli` is no longer under active development. - This form is for bugs in the legacy `sentry-cli`. We will only consider a bug report here if you also have a concrete reason why using the new CLI is impossible or infeasible. That reason is separate from the legacy CLI bug you are reporting below. + If you find a bug in the new CLI, please [report it in the new CLI repository](https://github.com/getsentry/cli/issues/new). We will still consider bugs reported here when a blocker prevents you from adopting the new CLI. - - type: textarea - id: migration-blocker + - type: checkboxes + id: tried-new-cli attributes: - label: Reason you cannot use the new Sentry CLI - description: Describe the concrete technical or operational situation that makes the new CLI impossible or infeasible for you. This does not need to be a bug in either CLI, but it must be independent of the legacy CLI bug reported below. A preference to keep using the legacy CLI is not sufficient. - placeholder: Describe the new CLI capability, compatibility requirement, environment constraint, or other blocker that prevents migration. - validations: - required: true + label: Have you tried the new Sentry CLI? + options: + - label: I have tried the new Sentry CLI. + required: true - type: checkboxes - id: migration-confirmation + id: adoption-blocker attributes: - label: Migration blocker confirmation + label: Is something blocking adoption of the new CLI? options: - - label: I have described a concrete reason, separate from the bug below, why I cannot use the new Sentry CLI instead. + - label: I encountered a blocker that prevents me from adopting the new Sentry CLI. required: true + - type: textarea + id: migration-blocker + attributes: + label: What is blocking your migration? + description: Tell us what makes adopting the new CLI impossible or infeasible for you. This does not have to be a bug in either CLI. + placeholder: Describe the missing capability, compatibility requirement, environment constraint, or other blocker. + validations: + required: true - type: markdown attributes: