We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
similar to this: https://github.com/scicloj/devcontainer-templates/tree/main/src/scicloj
(not needed things can be removed, if needed)
-> Makes hacking on libpython-clj a bit easier.
libpython-clj
The setup as well be re-used for a test suite with GitHub actions. But not sure it would simplify this a lot: https://github.com/clj-python/libpython-clj/blob/master/.github/workflows/test.yml
Devcontainer have different "philosophy". Instead of testing all JDKs, we "freeze to one".
See here for reference: https://github.com/scicloj/clojisr/blob/master/.github/workflows/ci.yml
The tests run "inside" the same devcontainer setup then the "project" has.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
similar to this:
https://github.com/scicloj/devcontainer-templates/tree/main/src/scicloj
(not needed things can be removed, if needed)
->
Makes hacking on
libpython-clj
a bit easier.The setup as well be re-used for a test suite with GitHub actions.
But not sure it would simplify this a lot:
https://github.com/clj-python/libpython-clj/blob/master/.github/workflows/test.yml
Devcontainer have different "philosophy". Instead of testing all JDKs, we "freeze to one".
See here for reference:
https://github.com/scicloj/clojisr/blob/master/.github/workflows/ci.yml
The tests run "inside" the same devcontainer setup then the "project" has.
The text was updated successfully, but these errors were encountered: