practicalli / practicalli/clojure
clj-kondo linting with CI server and GitHub/Lab commits
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
GitHub actions
solutions on the GitHub marketplace https://github.com/marketplace/actions/setup-clj-kondo
Or you can just include clj-kondo in your own GitHub action
https://rymndhng.github.io/2020/04/03/Integrate-clj-kondo-with-Github-Actions/
https://github.com/marketplace/actions/clj-kondo-checks
Using clj-kondo with CircleCI?
- is that too late?
- useful as an added safety check if someone ignores a github action advice?
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 reviewing the GitHub Marketplace links and the linked GitHub Actions article, then compare the proposed GitHub Actions and CircleCI approaches. The issue does not name files, tests, or a specific implementation target; completion would require clarifying whether to add CI configuration, documentation, or both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100