Adam Azarchs

No I don't have a draft; it's not to make a grammar for it but I wasn't going to bother without confirmation that it would be likely to get accepted....

Our main use cases are tagging the source (e.g. GitHub repo, pypi package, rust crate, etc.) and version information. We also usually add in whatever other package metadata is convenient...

I do think that no matter how comprehensive a fixed set of attributes you come up with, companies are going to have their own idiosyncratic use cases which aren't covered....

Honestly we don't change our dependency versions often enough for it to be a big problem (except maybe in some of the CI builders which don't keep a persistent cache),...

It seems to me like think that documentation is misleading. Pretty much any use of `ctx.path` seems to cause a restart, even if the argument you pass is a declared...

> You can't use the variables from the workspace file in an output file name. This is generally not a blocker. It's not hard to have a CI system do...

Are you suggesting running a bazel build that modifies the source tree to generate a bzl file using stamping information, and then running a second build that uses that? That...

That sounds rather dangerous to me, as I'm not aware of any documented contract that says that the workspace status command will always be evaluated before the loading phase, or...

Your statement of the problem makes the solution clear - starlark does not have access to the required information, which means that the renames can't be done in starlark. But...

This is just waiting for someone with permission to actually review and (hopefully) merge it (the test failures shown in the checks output were present on master as well at...