silverwind

I'm undecided. Think at least the stripes need to be wider to make an impact on these small lables, maybe 2-3px per stripe.

Maybe like this: ```css /* label with black text */ repeating-linear-gradient(-45deg, transparent, transparent 6px, #fff5 6px, #fff5 12px) /* label with white text */ repeating-linear-gradient(-45deg, transparent, transparent 6px, #0005 6px,...

So yes, I think it could work. You would need to use the CSS [multiple backgrounds feature](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_backgrounds_and_borders/Using_multiple_backgrounds), and it could either be added as inline style like current `color` is...

For testing one could do a very dirty kind of CSS selector: ```css .archived-label[style^="color: #fff"] { background-image: repeating-linear-gradient(-45deg, transparent, transparent 6px, #0005 6px, #0005 12px); } .archived-label[style^="color: #000"] { background-image:...

@delvh this is not ready yet 😆.

I'm seeing such intermittent hash failures on CI, which is a completely fresh environment, no cache involved. Happens about 1 in 10 runs it seems, and always on the same...

> hi. can try [this](https://gist.github.com/seyanaracore/a627fb40a82cd1bf02d3f275c2cb3d77) Maybe you want to contribute this. It may be okay to have it as a separate option to `sourcemapIgnoreList`, for compatibilty's sake.

These name limitations are intentional to keep compatibilty with other forges like GitHub etc. See https://github.com/go-gitea/gitea/issues/4150#issuecomment-2142191169 for some recent research on repo/org names. I guess it'd be fine to make...

Recent filesystems handle unicode pretty well, but still it's likely better to not let the user unknowingly break the portability of their repos.