- Notifications
You must be signed in to change notification settings - Fork 115
[Openapi] Change product feature output #4860
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
Conversation
| Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
miguelgrinberg left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I can't find any references to this x-metaTags extension anywhere. I assume this is another extension we have created that we'll ask Bump to implement for us?
| @miguelgrinberg yes exactly, they don't want to support |
| The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-8.19 8.19 # Navigate to the new working tree cd .worktrees/backport-8.19 # Create a new branch git switch --create backport-4860-to-8.19 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 47d6b76c2636d7c142567fc8bc61d5367902ff76 # Push it to GitHub git push --set-upstream origin backport-4860-to-8.19 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-8.19Then, create a pull request where the |
| The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-9.0 9.0 # Navigate to the new working tree cd .worktrees/backport-9.0 # Create a new branch git switch --create backport-4860-to-9.0 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 47d6b76c2636d7c142567fc8bc61d5367902ff76 # Push it to GitHub git push --set-upstream origin backport-4860-to-9.0 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-9.0Then, create a pull request where the |
| The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-9.1 9.1 # Navigate to the new working tree cd .worktrees/backport-9.1 # Create a new branch git switch --create backport-4860-to-9.1 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 47d6b76c2636d7c142567fc8bc61d5367902ff76 # Push it to GitHub git push --set-upstream origin backport-4860-to-9.1 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-9.1Then, create a pull request where the |
| manually backporting |
Changing the "product feature" property to something bump can support. Followup of #4511