python-poetry / python-poetry/poetry-plugin-export
Feature Request: Adding @generated to header of exported requirements files
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 335
- Forks
- 57
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 3
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the FAQ and general documentation and believe that my question is not already covered.
Feature Request
We benefited greatly from python-poetry/poetry#2773 and I think adding it to the exported requirements files would be a great idea as well.
I would be happy to tackle this.
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 locating the code paths that generate exported requirements files and review the behavior requested in python-poetry/poetry#2773. Confirm which export formats are affected; done means each applicable generated requirements file includes the requested @generated header without changing dependency output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100