Skip to content

Conversation

tecimovic
Copy link
Contributor

In case of self-hosted runner, the organization uses the
GitHub runner, but they also have their own self-hosted runner
"version", with specific configuration being improved over time
and through this increasing their own internal "runner version".

The way the message was written, sometimes results in
confusion, where developer and a devops person start mistakenly
assuming that the version is related to their own runner version,
and not the actual GitHub runner that runs on that hardware.
Time is then lost, until someone realizes that this has nothing
to do with the internal "runner version" itself, but with the
actual GitHub runner that needs to be upgraded.

Message was fixed to explicitely differentiate between
"GitHub runner" and the self-hosted runner itself to avoid
possible confusion and possibly save someone few minutes of time.

@tecimovic tecimovic requested a review from a team as a code owner November 26, 2024 18:35
In case of self-hosted runner, the organization uses the
GitHub runner, but they also have their own self-hosted runner
"version", with specific configuration being improved over time
and through this increasing their own internal "runner version".

The way the message was written, sometimes results in
confusion, where developer and a devops person start mistakenly
assuming that the version is related to their own runner version,
and not the actual GitHub runner that runs on that hardware.
Time is then lost, until someone realizes that this has nothing
to do with the internal "runner version" itself, but with the
actual GitHub runner that needs to be upgraded.

Message was fixed to explicitely differentiate between
"GitHub runner" and the self-hosted runner itself to avoid
possible confusion and possibly save someone few minutes of time.
@TingluoHuang TingluoHuang force-pushed the versioning-warning-message-ambiguity branch from 20b2144 to ed047eb Compare March 14, 2025 20:07
@TingluoHuang TingluoHuang enabled auto-merge (squash) March 14, 2025 20:07
@TingluoHuang TingluoHuang merged commit 8131246 into actions:main Mar 14, 2025
8 checks passed
sirredbeard pushed a commit to sirredbeard/runner that referenced this pull request Jun 11, 2025
sirredbeard pushed a commit to sirredbeard/runner that referenced this pull request Jun 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants