Skip to content

[AutoDevNext] FFCLEANUP-71041 Resolve stale flag atlascode-rovodev-entitlement-notification - #1886

Open
atlassian[bot] wants to merge 1 commit into
mainfrom
autodevnext/FFCLEANUP-71041-resolve-stale-flag-atlascode-rovodev-entitlement-notification
Open

[AutoDevNext] FFCLEANUP-71041 Resolve stale flag atlascode-rovodev-entitlement-notification#1886
atlassian[bot] wants to merge 1 commit into
mainfrom
autodevnext/FFCLEANUP-71041-resolve-stale-flag-atlascode-rovodev-entitlement-notification

Conversation

@atlassian

@atlassian atlassian Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

🤖 This PR was generated by AutoDev bot. For any help or concerns, reach out on #devai-autodev-community.

Action needed: please review, approve, and merge if this PR is ready. AutoDev will not automatically merge/decline it. We collect decline feedback to improve quality. Thanks!
Changes needed or questions? Leave comments. Autodev now addresses PR comments every few hours.

Summary

Resolves stale feature flag atlascode-rovodev-entitlement-notification (stale since 2025-12-26).

The flag's final value was true, meaning entitlement notifications should always be shown. This PR bakes that behaviour in permanently by removing the flag check.

Changes

  • src/util/features.ts: Removed RovoDevEntitlementNotification = 'atlascode-rovodev-entitlement-notification' from the Features enum.
  • src/util/rovo-dev-entitlement/rovoDevEntitlementChecker.ts: Removed Container.featureFlagClient.checkGate(Features.RovoDevEntitlementNotification) call and !showNotification guard from triggerEntitlementNotification(). Removed unused Features import.
  • src/util/rovo-dev-entitlement/rovoDevEntitlementChecker.test.ts: Removed unused mockFeatureGateClient mock and featureFlagClient Container assignment.
  • CHANGELOG.md: Added entry for this cleanup.

Behaviour

No user-facing behaviour change — entitlement notifications were already always shown (flag was true). The remaining guards (jira.enabled, isBoysenberryMode, _enabled, rovodev.enabled) are preserved.

Recent PR change-site overlap

The clash check via TWG was inconclusive because this repository is hosted on GitHub, not Bitbucket. No manual overlaps were detected for the changed files (src/util/features.ts, src/util/rovo-dev-entitlement/rovoDevEntitlementChecker.ts).

Resolves: FFCLEANUP-71041


Rovo Dev code review: Rovo Dev couldn't review this pull request
Rovo Dev does not review pull requests created by bot accounts.

…ent-notification

Remove the stale feature flag 'atlascode-rovodev-entitlement-notification'
from the Features enum and refactor triggerEntitlementNotification() to
remove its dependency on the flag check.

The flag's final value was 'true', so notifications are now always enabled
(subject to existing guards: jira.enabled, isBoysenberryMode, _enabled,
and rovodev.enabled). This makes the previously flag-gated behaviour the
permanent default without any change in user-facing behaviour.

- Removed RovoDevEntitlementNotification from Features enum in features.ts
- Removed Container.featureFlagClient.checkGate() call and showNotification
  guard from triggerEntitlementNotification() in rovoDevEntitlementChecker.ts
- Removed unused 'Features' import from rovoDevEntitlementChecker.ts
- Cleaned up unused mockFeatureGateClient in the corresponding test file
- Added CHANGELOG entry

Resolves: FFCLEANUP-71041
@atlassian-cla-bot

Copy link
Copy Markdown

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌rayCodingNow

Already signed the CLA? To re-check, try refreshing the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant