clj-python / clj-python/libpython-clj
add .devcontainer setup
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1.2k
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the scicloj devcontainer-templates example and clojisr's .github/workflows/ci.yml with libpython-clj's .github/workflows/test.yml. Identify the minimal setup needed for hacking on libpython-clj and for running its tests inside the devcontainer. Done means the repository has a usable .devcontainer setup and the relevant tests can run with it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd, developer-experience, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100