Story #4713
As a user, I can specify Remote.includes with a pipenv.lock files
Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Target Release - Python:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:
Description
This is identical to the requirements.txt workflow, but with pipenv.lock files
Related issues
History
#1
Updated by amacdona@redhat.com almost 2 years ago
- Copied from Story #4711: As a user, I can specify Remote.includes with a requirements.txt added
#2
Updated by CodeHeeler over 1 year ago
- Sprint Candidate changed from No to Yes
#3
Updated by dalley 8 months ago
- Related to Story #4690: Implement package locking / digest specification added
#4
Updated by dalley about 1 month ago
- Sprint/Milestone deleted (
3.0 GA)
Please register to edit this issue