faker
faker copied to clipboard
Published
20 hours ago •
faker-js
faker-js
docs: backport docs changes to v8 branch
Backports to the following changes to v8 branch so that the main fakerjs.dev website can be updated without needing to wait for v9 release.
- docs: add donate links (#2806)
- docs: use new X icon instead of twitter icon in social links (#2825)
- docs: update roadmap for v9 (#2802)
- docs: improve contributing guide (#2747)
Deploy Preview for fakerjs ready!
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | 26d03ccbf823600f98c1c01a3a6c7c780808946f |
| Latest deploy log | https://app.netlify.com/sites/fakerjs/deploys/66270c4f3c77200008468aff |
| Deploy Preview | https://deploy-preview-2847.fakerjs.dev |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
If we choose this strategy of backporting, we will never --ff-only again
If we choose this strategy of backporting, we will never
--ff-onlyagain
Is it likely that we will need to merge into v8 in future? Most likely seems to be
- Minor website updates like this
- A super-critical bugfix requiring a 8.4.2 release
Is there an alternative to cherry-picking that keeps the history more clear?
