robotpy / robotpy/robotpy-installer

Maybe robotpy init should update existing pyproject.toml files if they don't already have tool.robotpy

Open
#97 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
6
Forks
18
Avg merge
34m
Merged PRs (30d)
1

Description

Use case would be users who already have a black/pytest/whatever config lying around.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start at the robotpy init entry point and inspect how it handles pyproject.toml files. The change is complete when an existing configuration preserves its black or pytest settings while adding tool.robotpy only when that section is absent; the payload names no test file to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.