ケイラ
should be mergable in the next few weeks as we approach the end of the orgs experiment
@lucacasonato has anyone been running into this still?
bug: Access to Workspaces across organizations requires specific permissions in primary organization
I just poked around and this all looks like it's working as intended to me. An important thing to note, an organization admin can only stop/update/manage workspaces that are built...
yeah, I noticed that. :\ and I've observed the behavior in normal day-to-day usage as well. since the tree walking is entirely outsourced to the [ignore](https://crates.io/crates/ignore), I have a feeling...
oh I think this was fixed in 1.1 btw
huh, interesting. I would've really expected this to be configurable from Trunk.toml. it feels really unintuitive to configure something like this inside the index.html, imho. kinda like a `Box`.
as a fix for this specific issue, I think it'd be nice if Trunk checked for Cargo.toml.. - Next to the index.html file (like it already does; this would take...
if you could point me at what files I should look in I might be able to work on it tonight :)
can you please rebase this on the latest trunk branch? there's an extra commit in here that adds duplicates of `min`, `max`, `step`, and `list`, which I already accepted in...
any chance a new version with the fix will be published soon?