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
docs: es6ify 'Breaking Changes' and 'File' API pages #15507
docs: es6ify 'Breaking Changes' and 'File' API pages #15507
Conversation
💖 Thanks for opening this pull request! 💖 We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix. Examples of commit messages with semantic prefixes:
Things that will help get your PR across the finish line:
We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can. |
@ntocampos Can you group all your ES6'ify PR's into one PR please? It'll make it easier to review in one go and will cause less CI jobs to run 👍 |
Sure. I'm gonna do this now 😄 |
Done. I've closed the other PR. |
b5968c5
to
e244c61
Compare
Release Notes Persisted no-notes |
Congrats on merging your first pull request! 🎉🎉🎉 |
Can I work on this issue? |
Description of Change
This pull-request "es6ifies" code snippets in the
Breaking Changes
andFile
object documentation pages, as suggested on #14842.cc @ckerr
Checklist
Release Notes
Notes: no-notes