Start here: contributions welcome

Open
  • Is something wrong?
#72 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
cli, developer-experience

Research direction

This is an index rather than a single change. Read CONTRIBUTING.md and the existing check pattern in src/devready/checks/runtimes.py, then use #64 as the worked example. Pick one open issue from the list, comment to claim it, and run pytest, ruff check and ruff format --check before opening a PR. Done means a claimed issue with a PR that passes those three checks.

Written by the indexing model from the issue text.

Description

good first issue help wanted

DevReady is small and new contributors are very welcome. Most new checks are one table row plus a small extractor in src/devready/checks/runtimes.py, so a first PR usually takes an evening.

How to start

  1. Pick an open issue below and comment to claim it. I will assign you, usually within a day.
  2. Read CONTRIBUTING.md and use #64 (Maven) or #65 (Gradle) as a worked example of a new check.
  3. One issue per PR. pytest, ruff check and ruff format --check must pass.

Open for contributors

  • #66 PHP version from composer.json
  • #67 Deno version from .dvmrc
  • #68 Terraform version from .terraform-version
  • #69 Dart SDK range from pubspec.yaml
  • #70 Java pin from .sdkmanrc
  • #71 Action CI: multi-id only and skip
  • #61 Exact fix --plan commands for nvm, pyenv, mise, asdf

Rules every check follows: read-only, no network, no new dependencies, never print file contents or env values.

Have an idea for another ecosystem? Open a feature request and name the file that declares the version.

Dominant language
Python
Stars
2
Forks
3
Avg merge
10h 51m
Merged PRs (30d)
40

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Evalogical-Inc/devReady

All issues in Evalogical-Inc/devReady

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.