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

v1.16: geyser: remove startup_status (backport of #230) #231

Merged
merged 2 commits into from
Nov 1, 2023

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Nov 1, 2023

This is an automatic backport of pull request #230 done by Mergify.
Cherry-pick of 8f1cc8b has failed:

On branch mergify/bp/v1.16/pr-230
Your branch is up to date with 'origin/v1.16'.

You are currently cherry-picking commit 8f1cc8b.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG.md
	modified:   yellowstone-grpc-client-nodejs/package.json
	modified:   yellowstone-grpc-geyser/src/plugin.rs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   Cargo.lock
	both modified:   Cargo.toml
	both modified:   examples/rust/Cargo.toml
	both modified:   yellowstone-grpc-client/Cargo.toml
	both modified:   yellowstone-grpc-geyser/Cargo.toml
	both modified:   yellowstone-grpc-proto/Cargo.toml
	both modified:   yellowstone-grpc-tools/Cargo.toml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/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> 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 added the conflicts label Nov 1, 2023
@mergify mergify bot assigned fanatid Nov 1, 2023
(cherry picked from commit 8f1cc8b)
@fanatid fanatid merged commit 365140d into v1.16 Nov 1, 2023
3 checks passed
@fanatid fanatid deleted the mergify/bp/v1.16/pr-230 branch November 1, 2023 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant