robotpy / robotpy/robotpy-installer
`robotpy deploy` will erase manually installed packages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 18
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
If the user specifies --no-deploy or they decline the sync, then they'll never run into this. But for users that want to use a manual workflow, this will be a problem since there isn't a manual deploy process that doesn't do a sync. Thinking about two alternatives:
- Add options to
pyproject.tomlto say "don't manage the packages on the rio" - Add a
robotpy installer deploywhich only deploys the code, and doesn't do all of the fancy things that therobotpy deploycommand does
... I'm sorta attracted to the second option because I'd rather not have configuration options. Maybe call it robotpy installer only-deploy or robotpy installer deploy-only? Sorta like with git having plumbing and porcelain commands.
Contributor guide
No contributing guide indexed for this repository
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 tracing the existing robotpy deploy command and the proposed robotpy installer deploy or deploy-only entry point. Compare the two proposed approaches and confirm how a manual workflow can deploy code without synchronizing packages. Done means a documented, tested path preserves manually installed packages while still deploying the code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100