Skip to content
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

chore: update vesting readme (backport #15107) #15108

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 20, 2023

This is an automatic backport of pull request #15107 done by Mergify.


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> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@mergify mergify bot requested a review from a team as a code owner February 20, 2023 23:19
@tac0turtle tac0turtle closed this Feb 20, 2023
@tac0turtle tac0turtle deleted the mergify/bp/release/v0.47.x/pr-15107 branch February 20, 2023 23:20
@julienrbrt
Copy link
Member

Why is this closed? I think we should show correct docs under /v0.47 too instead of only /main

@tac0turtle
Copy link
Member

oh i thought versioning with docusauours was all on main, i thought we were doing this only for the vue items (0.45,0.46). Ideally we only backport what is needed so we can audit the commits better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants