-
Notifications
You must be signed in to change notification settings - Fork 193
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
ci(e2e-wasm.yml): rm unused workflow #1723
Conversation
Warning Rate Limit Exceeded@Unique-Divine has exceeded the limit for the number of files or commits that can be reviewed per hour. Please wait 15 minutes and 10 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the @coderabbitai review command. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. WalkthroughThe latest update in the repository includes a single change that streamlines the CI process. A commit was made to the NibiruChain project, which involved the removal of an unused workflow file, specifically Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ? TipsChat with CodeRabbit Bot (
|
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.
Purpose / Abstract
The GH action defined in
e2e-wasm.yaml
has been silently failing for monthsand showing a passing state without executing logic. I believe we originally
added it to verify that we wired in the
x/wasm
module properly fromgithub.com/CosmWasm/wasmd, but we test this in many ways now. For example,
there are e2e contract tests in
x/tokenfactory
using real smart contracts.It's safe to delete this file because it wasn't even running.
Summary by CodeRabbit
Chores
Documentation