feature-branch-deployment: Add the possibility to request upgrading f… #6111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6111 +/- ##
==========================================
+ Coverage 66.72% 66.74% +0.01%
==========================================
Files 540 540
Lines 64180 64180
Branches 5240 5242 +2
==========================================
+ Hits 42827 42834 +7
+ Misses 21353 21346 -7 ☔ View full report in Codecov by Sentry. |
sbocahu
added
the
do not merge
…rom a 5.8 version
sbocahu
force-pushed
the
featurebranch-upgrade-from-58
branch
from
f5116bb
to
458a4ec
Compare
sbocahu
removed
the
do not merge
|
@Kedae tested from a fork; ready for merge IMHO |
Kedae
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…rom a 5.8 version
Proposed changes
Related issues
Checklist
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...