-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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: update docs for 10.0 api, configuration #14710
Conversation
My preference here would be to not squash this PR, but do a ff-only merge. Can you rewrite this commit: docs: reintroduce changes to flows for 10.0 to contain a (#PR) tag in the message? |
Unfortunately no because it was never a PR. It was just an extra commit that I added hastily. |
This PR number is sufficient |
7264c75
to
0612a31
Compare
0612a31
to
967d08e
Compare
ff0fcd6
to
4919438
Compare
4919438
to
f83bd29
Compare
ce47e4f
to
21faad2
Compare
21faad2
to
7166a66
Compare
72a10c2
to
e6e8f5a
Compare
The PRs that merged to
10-docs-staging
branch are here.Related #14586
This should be one of the last things we merge for 10.0 so our latest release isn't behind our docs for too long, we could even do it after 10.0. The commit log includes various PRs that were approved individually, but we can still make changes here.