Standardize Hash ID Format in requirements.txt
Open
dependencies
- Dominant language
- Python
- Stars
- 30
- Forks
- 22
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 22
Description
# 💡 Summary #
Use either full hash or partial hash for consistency.
See https://github.com/cisagov/XFD/pull/82#discussion_r1529100038
Contributor guide
Research direction
Read requirements.txt and the linked PR #82 discussion first. Determine the agreed hash convention, apply it consistently in requirements.txt, and confirm the file no longer mixes formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100