As a user, I can specify Remote.includes with a pipenv.lock files
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Python
- Stars
- 49
- Forks
- 88
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 31
Description
Original Pulp Redmine Issue: https://pulp.plan.io/issues/4713
This is identical to the requirements.txt workflow, but with pipenv.lock files
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 locating the existing requirements.txt workflow for Remote.includes in this repository, then review the linked Pipenv documentation and the original Redmine issue. Done means Remote.includes handles pipenv.lock files with behavior matching the requirements.txt workflow, including appropriate test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100