-
Notifications
You must be signed in to change notification settings - Fork 52
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
request: other options aside from code checks which isn't under active development anymore #69
Comments
Agree. I love codechecks so much. Tears. And more tears. |
@cgewecke any ideas for some kind of a similar setup? I'd really like to see this. |
Yes. I think there is (theoretically) a way to do it without an external service (Chris Kaczor the codechecks maintainer suggested this to me a couple years ago...) You would use your CI service's artifacts or long-term storage API as a simple file "database". Check results would be stored there instead of on the codechecks backend. CircleCI has an API like this and I believe Github actions has one too: https://circleci.com/docs/2.0/artifacts/ I think it should be possible to trigger Github checks within CI somehow...like maybe by spinning up a Probots dev instance as part of the CI run. (That might be more complicated than it needs to be). In the worst case you would need to host your own probots service in the cloud somewhere. An example of a probots github check that uses a similar feature set to CodeChecks is here: https://github.com/tianhaoz95/check-group I would also love to see a free standing solution for this worked out. One note... I think Codechecks received some funding from OptimismPBC so maybe it will see further development. Not sure what the status of the optimism grants is exactly - this project was also awarded something but idk if they've distributed anything yet or not. |
As the title suggests, code checks is no longer under active development. It would be great to have some other options here.
The text was updated successfully, but these errors were encountered: