-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 REST endpoints in migration docs (bp #8648) #8687
Conversation
* fix endpoints * update docs * fix routes * update docs Co-authored-by: Anil Kumar Kammari <anil@vitwit.com> (cherry picked from commit 897f20b) # Conflicts: # docs/migrations/rest.md
@alessio please merge. whats the reason to block merging stuff like this into releases. Do we really think this is a security concern? |
? |
Why do we have to block merges into the release branch. I guess this goes into a discussion of expanding the people who can merge things to more than just three, or we clone you. |
I agree. I'll open a PR @marbar3778 👍 |
This is an automatic backport of pull request #8648 done by Mergify.
Cherry-pick of 897f20b has failed:
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.io/