Restructure Directory Tree
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 148
- Forks
- 55
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Feature Request
We dont really need the workflow/ directory, and move up all the subdirectories. Moreover, we can probably get rid of the report/ directory
Suggested Solution
No response
Additional Info
No response
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 inventorying the current workflow/ and report/ directories and their subdirectories to understand the proposed target tree. Check the repository for anything that depends on those paths before deciding whether the restructure is safe. Done means workflow/ and report/ are removed, their intended contents are moved up, and the project remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100