Roberto Villarreal

@alexcb FYI, this didn't get automatically closed. [It appears](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) that you have to repeat the keyword ("close 1, close 2") for each issue. Only the first issue you mentioned (not...

@alexcb Maybe there is another way to tackle this. It probably deserves its own standalone issue/request (and I probably will open an issue at some point), but to ease into...

I discovered this issue via the linked PR (which is what caught my attention). I thought I'd add another scenario where this feature might be useful, though kubernetes is not...

I believe I've stumbled upon this as well. I have some other non-trivial things happening in my setup as well, so it took me a while to think that it...

I can also add that what matters is where the `SAVE IMAGE --push` is defined, not the target that's invoked. In other words, doing ```Earthfile foo: BUILD +github.com/remote/project+target ``` with...

I was trying to diagnose an unrelated issue, but in the process, came across the code that dictates what's saved/pushed. There's a couple places that are candidate culprits (to my...

There's a distinction between log uploads/sharing (whether to transmit or not) and stream/non-stream (technical mechanism for transmitting, if/when requested). I believe that changelog entry is only about the latter (as...

I can see where project-level configs (or 'tiered' configs) would be nice (like your use-case of having the project disable uploads on behalf of users), but many settings don't make...

Yeah, I had uncovered that same control sequence in my report (I know my tendency to be thorough can result in stuff getting overlooked and have the opposite effect...). However,...

I decided to take up the quest again for a little bit. It turns out there's one other place in the codebase where that sequence is defined. And out of...