onepub-dev / onepub-dev/pub_release
multi release must only tag once for a mono repo
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 18
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
When doing a multi package release in a mono repo we are currently tagging the repo for each project but its in the same repo so this makes no sense.
We need to change the tagging code so that it only tags the repo once.
We need to be smart about this as multi should work for mono and non-mono repos.
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 multi-package release tagging path in the Dart CLI and trace how it distinguishes mono-repository and non-mono releases. Verify that a mono repo receives one repository tag while multi-package releases in non-mono repos retain their existing tagging behavior; add or update the relevant tests if the project has coverage for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100