** This One YAML Key Makes GitHub Actions Workflow Runs Easy to Identify **
I've been using github actions for years now and recently discovered this hack. It's so easy that I hated myself for not knowing it.Manual deployments through workflow_dispatch are common. They also create a visibility problem that most teams only notice when something breaks. When every run is labelled Deploy, the Actions list stops being an operations surface and becomes a set of identical rows. The version, the environment, and the person who triggered the change sit inside the run — not on it.During an incident, that list is where engineers go first. If you cannot tell which row reached production, you spend the opening minutes of the response answering the wrong questions: who changed what, and where.
Top comments (0)