Skip to content

feat(git-node): rebase staging commits after promoting a release #934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 20, 2025

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented May 19, 2025

If there are commits on the staging branch, we probably want to keep them on top of the release commit. Staging branches and release proposal are usually in sync, however it's never the case for security releases.

If there are commits on the staging branch, we probably want to keep
them on top of the release commit. Staging branches and release proposal
are usually in sync, however it's never the case for security releases.
Copy link

codecov bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.76%. Comparing base (52994d8) to head (b5040a6).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #934   +/-   ##
=======================================
  Coverage   79.76%   79.76%           
=======================================
  Files          39       39           
  Lines        4630     4630           
=======================================
  Hits         3693     3693           
  Misses        937      937           

☔ 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.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aduh95 aduh95 merged commit 197134f into nodejs:main May 20, 2025
15 checks passed
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.

2 participants