-
Notifications
You must be signed in to change notification settings - Fork 930
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: use redis for ci/cd #1905
ci: use redis for ci/cd #1905
Conversation
Co-authored-by: Aaron Dewes <aaron@runcitadel.space>
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.
I'm not sure if it's worth it, this should rather be a test that we add to the throttle plugin. I think this functionality is out of scope for Probot. If we want to test it then we should do an end-to-end test.
I would actually have atleast one test against redis. Just to ensure, that there are no side effects because of the use of redis. |
Any way we could add a test with REDIS in CI only? Like a smoke test? Without polluting package.json and our existing tests? |
Yes |
Co-authored-by: Aras Abbasi <aras.abbasi@googlemail.com>
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.
Thanks!
Yay! |
🎉 This PR is included in version 13.0.0-beta.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Lets see if this works. But if it works, we can test the redis code too ;).
Maybe just test against redis 7?