Skip to content

Drop cherry-pick call-to-action from hotfix branch list in merge messages#266

Merged
charlesprost merged 1 commit intomainfrom
fix/hotfix-left-untouched-message
Apr 21, 2026
Merged

Drop cherry-pick call-to-action from hotfix branch list in merge messages#266
charlesprost merged 1 commit intomainfrom
fix/hotfix-left-untouched-message

Conversation

@charlesprost
Copy link
Copy Markdown
Contributor

Summary

  • queued.md and successful_merge.md were telling developers to open a cherry-pick PR to every phantom hotfix branch in the cascade — which can be dozens of old, finished post-GA branches (e.g. scality/Integration#1426 showed 29 hotfix branches).
  • The cherry-pick call to action is only correct when the Jira ticket explicitly carries a hotfix fix version (already handled by the separate PendingHotfixVersionReminder comment, code 223).
  • The merge/queued messages now simply state the branches were not targeted and were left untouched, with no action required.

Before:

⚠️ This pull request did not target the following hotfix branch(es). Please open a separate cherry-pick pull request to each: ...

After:

This pull request did not target the following hotfix branch(es) so they were left untouched: ...

Test plan

  • CI green
  • test_dev_pr_reminder_about_pre_ga_hotfix still passes (branch name still appears in message)

🤖 Generated with Claude Code

…ages

The queued/successful_merge templates were telling developers to open a
separate cherry-pick PR to every phantom hotfix branch in the cascade.
This is wrong: the repo can have dozens of old post-GA hotfix branches,
none of which need a cherry-pick from this PR.

The cherry-pick reminder is only appropriate when the Jira ticket
explicitly carries a hotfix fix version (handled separately by
PendingHotfixVersionReminder). The merge messages should simply note
that the hotfix branches were not targeted and were left untouched,
with no call to action.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@charlesprost charlesprost requested a review from a team as a code owner April 21, 2026 07:30
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.28%. Comparing base (f955646) to head (9ac360e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #266   +/-   ##
=======================================
  Coverage   89.28%   89.28%           
=======================================
  Files          77       77           
  Lines       10287    10287           
=======================================
  Hits         9185     9185           
  Misses       1102     1102           
Flag Coverage Δ
integration 87.51% <ø> (ø)
tests 87.47% <ø> (ø)
tests-BuildFailedTest 26.79% <ø> (ø)
tests-QuickTest 34.38% <ø> (ø)
tests-RepositoryTests 26.45% <ø> (ø)
tests-TaskQueueTests 51.66% <ø> (ø)
tests-TestBertE 65.59% <ø> (ø)
tests-TestQueueing 53.90% <ø> (ø)
tests-api-mock 15.81% <ø> (ø)
tests-noqueue 77.63% <ø> (ø)
tests-noqueue-BuildFailedTest 26.79% <ø> (ø)
tests-noqueue-QuickTest 34.38% <ø> (ø)
tests-noqueue-RepositoryTests 26.45% <ø> (ø)
tests-noqueue-TaskQueueTests 51.66% <ø> (ø)
tests-noqueue-TestBertE 61.95% <ø> (+0.01%) ⬆️
tests-noqueue-TestQueueing 26.48% <ø> (ø)
tests-server 29.12% <ø> (ø)
unittests 41.63% <ø> (ø)
utests 25.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@charlesprost charlesprost merged commit 24545a4 into main Apr 21, 2026
18 checks passed
@charlesprost charlesprost deleted the fix/hotfix-left-untouched-message branch April 21, 2026 08:11
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