python-poetry / python-poetry/poetry-plugin-export
feat: Development Docs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 335
- Forks
- 57
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 3
Description
Hello!
I would like to develop a new output type. Can provide as a PR when done.
In embarking on this, I'm scratching my head a bit on development flow. Any chance someone could append a development section to the README.md? I will figure it out regardless, but the assist out-of-the-gate would be lovely for myself and future devs who want to put their weight behind this!
If I figure out a tidy enough flow I will PR that as well. But if someone out there has a "this is how I implement in this repo" already in mind 🙏 .
Thanks!
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
Review README.md and the repository layout to understand the development flow relevant to adding a new output type. Document that flow in a new development section, with enough guidance for future contributors to get started; done means the README clearly explains how to develop in this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100