bukinoshita / bukinoshita/git-labels-cli
git-labels does not always persist all labels
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I've been testing the usage of `git-labels-cli` today, as I'd like a simple version of GitHub label management that I can have run during my CI builds to ensure labels are always up-to-date on our project.
However, I'm noticing that after `git-labels-cli` removes all labels it doesn't always successfully create the new ones. This is certainly problematic if I'm going to use this during automated builds. Sometimes after I run the script I have 13 out of 16 labels, sometimes it's 14, 15, and sometimes it's the full 16.
I'm also seeing this error occasionally:
```
git-labels --file .github/labels.json marcaddeo/Test-Labels
> Error! Validation Failed (422)
```
Do you have any ideas on how to stabilize this to ensure labels are always created as outlined in my labels file? It's important to me that these operations be idempotent so I can use them in an automated fashion.
Thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the command `git-labels --file .github/labels.json marcaddeo/Test-Labels` with the 16-label file and observe the intermittent missing labels and 422 validation error. Trace the label removal and creation flow, then verify that repeated runs consistently leave all 16 labels present without validation failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100