Jordan Baxter
Jordan Baxter
@swanandx could you take a look at this?
@tekjar bumping this
> > `type=raw,value=latest,enable=${{ inputs.is-latest }}` > > Do you repro as well with `type=raw,value=latest,enable=false`? If not then that might be related to how GitHub handles boolean inputs. Yea that question...
>It's a subtle bug that the README should probably highlight better I think a louder warning or an action failure when processing special case tags would better. Something that points...
Yea I think any tags that can be listed in the `tags` section whose behavior can be influenced by another setting should come with a warning if there are conflicting...
I'm ultimately apathetic about it though as I rarely work on CI these days. Feel free to close this if you don't want to use it as a tracking issue.
Mainly repository hygiene. I could add a script at the root of each package that accesses the `WORKSPACE_ROOT` env var to call the main pre-release hook. But that option requires...
> It sounds like you want one post-workspace-release hook but instead you run a hook after every package. Running a hook before every package is what is happening, but was...
A representative package *could* work for my use case. But tbh I think that would come with a bit of a code smell. Hard to explain, but I don't think...
> Any thoughts on how to improve this? I think the source of confusion is that the `[workspace.metadata.release]` table is overloaded, and careful review of the docs is required for...