-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
fix: Replace broken goo.gl link with actual docs link #14081
base: main
Are you sure you want to change the base?
Conversation
Hi @legobeat! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a breaking change, so cannot be done until the next major.
the URL also seems broken - it's supposed to point to https://jestjs.io/docs/snapshot-testing
/easycla |
@SimenB How would this be breaking? Fixed the broken link. |
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Only in this PR almost 150 snapshots are not passing. Now imagine Renovate bot upgrading Jest: all snapshot users will get red CIs (because snapshots are not updated in CI). This simply should not happen between minor releases. |
By the way, you should include change log entry too. |
If CI indeed breaks, it would be very helpful if the workflow could be approved. |
Where should a log be added, apart from bddff35? |
Do you speak about the CI in this repo? This will pass. I had in mind the CIs which run Jest for users in repos which are being updated by bots like Renovate. |
These two are changing something in this repo only (because lock file or snapshots are not shipped to NPM). The change you are making will be shipped to the users. In other other words, the changes you are referring have zero impact on code of |
c58cffa
to
aced412
Compare
Looks good for my eye. Thanks! |
Fixed changelog conflict. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
You don't have to keep this conflict free btw - I'll deal with it when I start landing breaking changes for v30 🙂
643a61f
to
e391ffd
Compare
Any updates? Google announced that they'll abondon all goo.gl links after August 25th, 2025: Google URL Shortener links will no longer be available - Google Developers Blog |
Summary
Test plan