-
Notifications
You must be signed in to change notification settings - Fork 174
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
MWPW-161273 Standalone Gnav needs a release cycle [Bundle] #3322
Conversation
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## stage #3322 +/- ##
==========================================
- Coverage 96.41% 96.41% -0.01%
==========================================
Files 246 246
Lines 57568 57567 -1
==========================================
- Hits 55505 55504 -1
Misses 2063 2063 ☔ View full report in Codecov by Sentry. |
This PR does not qualify for the zero-impact label as it touches code outside of the allowed areas. The label is auto applied, do not manually apply the label. |
c32f880
to
4ec39cf
Compare
Validated the changes on the pr, details are added in the ticket https://main--blog--adobecom.hlx.page/?milolibs=bundled-standalone-gnav-fix https://main--cc--adobecom.hlx.page/creativecloud?milolibs=bundled-standalone-gnav-fix redirection on the link is working Validation is done on bacom/blog and blog and regression on cc, dc,home and bacom |
Skipped 3322: "MWPW-161273 Standalone Gnav needs a release cycle [Bundle]" due to file "libs/blocks/global-footer/global-footer.js" overlap. Merging will be attempted in the next batch |
Resolves: MWPW-163734
Test URLs: