MerginMaps / MerginMaps/work-packages
Adding new entries into .yml creates completely empty work-package
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I have (for example) 5 work-packages, all of which have 2 files (.gpkg and .qgz) and sync perfectly fine.
Then I edit the .yml to add an additional work-package, which then creates the work-package, but with no files in.
Work-package syncing then fails because the new work-project doesn't have a .gpkg.
Contributor guide
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
Reproduce the problem by adding a work-package to the YAML while syncing the existing packages, then trace the creation and sync path for the new package. Confirm the fix by verifying that the new package receives its expected .gpkg and .qgz files and that syncing completes without failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100