-
Notifications
You must be signed in to change notification settings - Fork 154
bfCache #3527
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
base: main
Are you sure you want to change the base?
bfCache #3527
Conversation
Datadog SummaryWas this helpful? Give us feedback! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3527 +/- ##
=======================================
Coverage 92.20% 92.21%
=======================================
Files 312 314 +2
Lines 8031 8065 +34
Branches 1814 1816 +2
=======================================
+ Hits 7405 7437 +32
- Misses 626 628 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
/to-staging |
View all feedbacks in Devflow UI.
Commit 707f265ba6 will soon be integrated into staging-20.
We couldn't automatically merge the commit 707f265ba6 into staging-20. What to do next?
If you think the errors come from a logical conflict with the target branch, you can create a fix by commenting this pull request with DetailsSince those jobs are not marked as being allowed to fail, the pipeline will most likely fail. |
/to-staging |
View all feedbacks in Devflow UI.
Commit 707f265ba6 will soon be integrated into staging-20.
Commit 707f265ba6 has been merged into staging-20 in merge commit ca3ffe09ba. Check out the triggered pipeline on Gitlab 🦊 If you need to revert this integration, you can use the following command: |
Integrated commit sha: 707f265 Co-authored-by: RomanGaignault <[email protected]>
Motivation
Changes
Test instructions
Checklist