More memorable run name generation

[garrett]

Thanks you for your input - that’s helpful!

I opened an issue so we can track progress on this.

User defined run identifiers

I also generated a stub for a more thorough consideration:

User defined run identifiers

Summary This RFC seeks input on the creation of a run identifier scheme that uses user-defined strings. No part of this RFC proposes breaking changes. This proposal is awaiting feedback Problem Guild uses run IDs in various applications: Uniquely identify a run in a list (e.g. guild runs) Identify a run when specifying an operation dependency (e.g. guild run test run=<run Id>) These run IDs are not meaningful or intuitive to users and therefore hard to use. Background Guild unique…

My intuition (for what it’s worth!) is pointing toward tags for this. Both git and docker use tags for user-facing identifiers. Guild already supports tags. I think what’s missing is a way to elevate tags (or a tag) as a type of run alias.

Note that Docker’s “name” vs “tag” language is a source of confusion, where a NAME:TAG tag convention has loaded meaningful. We should look closely at this.

Please feel free to weigh in with your thoughts here or the RFC above. The GitHub issue is just to help track our work on this topic.

Thanks again to everyone here for the contribution!