Skip to content

feat(integrations): Expose SCM toggles in integration config UI#113923

Merged
evanpurkhiser merged 1 commit intomasterfrom
evanpurkhiser/feat-integrations-expose-scm-toggles-in-integration-config-ui
Apr 29, 2026
Merged

feat(integrations): Expose SCM toggles in integration config UI#113923
evanpurkhiser merged 1 commit intomasterfrom
evanpurkhiser/feat-integrations-expose-scm-toggles-in-integration-config-ui

Conversation

@evanpurkhiser
Copy link
Copy Markdown
Member

@evanpurkhiser evanpurkhiser commented Apr 24, 2026

Part of Phase 3 of VDY-110. Adds pr_comments (GitHub + GitLab) and nudge_invite (GitHub only) descriptors to get_organization_config(), so each install exposes its own toggles in the standard integration config form rather than through org-level options.

Both descriptors are appended after the integrations-issue-sync disabling loop — PR-comment and missing-member detection are self-serveable regardless of issue-sync entitlement, so we intentionally skip the feature gate applied to the other config fields.

Ref: VDY-113: Phase 3: Move SCM settings UI to per-install integration config

Migration phases

  • ● Phase 1 — Backfill existing OIs: #113841 (merged)
  • ● Phase 1 — Backfill cross-silo fix: #113908
  • ● Phase 1 — Dual-write SCM toggles: #113842
  • ● Phase 2 — Read from OI config behind flag: #113864
  • ○ Phase 3 — Expose toggles in per-install UI: (This PR)
  • ○ Phase 3 — Remove legacy detail-view toggles (frontend): upcoming
  • ○ Phase 3 — Drop SCM toggle fields from PUT endpoint: upcoming
  • ○ Phase 4 — Remove legacy code paths: upcoming

Part of Phase 3 of VDY-110. Adds pr_comments (GitHub + GitLab) and
nudge_invite (GitHub only) descriptors to get_organization_config(),
so each install exposes its own toggles in the standard integration
config form rather than through org-level options.

Both descriptors are appended after the integrations-issue-sync
disabling loop — PR-comment and missing-member detection are
self-serveable regardless of issue-sync entitlement, so we intentionally
skip the feature gate applied to the other config fields.

Fixes: [VDY-113](https://linear.app/getsentry/issue/VDY-113/phase-3-move-scm-settings-ui-to-per-install-integration-config)
@evanpurkhiser evanpurkhiser requested a review from a team as a code owner April 24, 2026 15:52
@evanpurkhiser evanpurkhiser requested a review from a team as a code owner April 24, 2026 15:52
@evanpurkhiser evanpurkhiser requested review from a team and wedamija April 24, 2026 15:52
@evanpurkhiser evanpurkhiser requested a review from a team as a code owner April 24, 2026 15:52
@linear-code
Copy link
Copy Markdown

linear-code Bot commented Apr 24, 2026

@evanpurkhiser evanpurkhiser merged commit 860163b into master Apr 29, 2026
62 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/feat-integrations-expose-scm-toggles-in-integration-config-ui branch April 29, 2026 20:31
evanpurkhiser added a commit that referenced this pull request Apr 29, 2026
…etail view (#113924)

Part of Phase 3 of VDY-110. The PR-comment and missing-member toggles
are now exposed in the per-install integration configuration form via
the standard JSONForm descriptors (landed in the prior backend commit,
[#113923](#113923)). Drop the
custom github/gitlab features tab on the integration detail page so the
two code paths don't compete.

The slack case in the same switch stays — slack alert-thread flags are
an out-of-scope anti-pattern tracked separately.

Ref: [VDY-113: Phase 3: Move SCM settings UI to per-install integration
config](https://linear.app/getsentry/issue/VDY-113/phase-3-move-scm-settings-ui-to-per-install-integration-config)
cleptric pushed a commit that referenced this pull request May 5, 2026
)

Part of Phase 3 of VDY-110. Adds pr_comments (GitHub + GitLab) and
nudge_invite (GitHub only) descriptors to `get_organization_config()`,
so each install exposes its own toggles in the standard integration
config form rather than through org-level options.

Both descriptors are appended after the integrations-issue-sync
disabling loop — PR-comment and missing-member detection are
self-serveable regardless of issue-sync entitlement, so we intentionally
skip the feature gate applied to the other config fields.

Ref: [VDY-113: Phase 3: Move SCM settings UI to per-install integration
config](https://linear.app/getsentry/issue/VDY-113/phase-3-move-scm-settings-ui-to-per-install-integration-config)
cleptric pushed a commit that referenced this pull request May 5, 2026
…etail view (#113924)

Part of Phase 3 of VDY-110. The PR-comment and missing-member toggles
are now exposed in the per-install integration configuration form via
the standard JSONForm descriptors (landed in the prior backend commit,
[#113923](#113923)). Drop the
custom github/gitlab features tab on the integration detail page so the
two code paths don't compete.

The slack case in the same switch stays — slack alert-thread flags are
an out-of-scope anti-pattern tracked separately.

Ref: [VDY-113: Phase 3: Move SCM settings UI to per-install integration
config](https://linear.app/getsentry/issue/VDY-113/phase-3-move-scm-settings-ui-to-per-install-integration-config)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants