You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or problem you’d like to solve
In case we aren't using the latest CLI version, every time we run the CLI locally or inside a CI job, we get a message like the next:
A new release of gh is available: 0.10.1 → v1.0.0
https://github.com/cli/cli/releases/tag/v1.0.0
This message is printed to the stderr (which generates unnecessary noise in CI jobs) and also it causes a small delay due to the external request, so we would like to be able to disable this check in some way.
Proposed solution
A switch to enable/disable the new release check. For example, by using an environment variable GHCLI_CHECK_UPDATES=<true|false> and/or a new boolean setting check_updates for the gh config command.
@danielfn This seems like a good idea to me. My preference would be to have both an environment variable and a configuration setting. I think GH_UPDATE_CHECK<disabled | enabled> for the environment variable and update_check<disabled | enabled> for the configuration setting sound good. cc @ampinsk for design input.
@danielfn Sorry for the nuisance! Agreed that there should be a way to disable the notifications. Furthermore, I think that update checks should never run in CI environments by default.
Closing as duplicate of #743 - follow that for updates!
@danielfn From the next release, update checker will be automatically disabled in CI environments (detected by the presence of environment variables such as CI) #2134
Activity
samcoe commentedon Oct 7, 2020
@danielfn This seems like a good idea to me. My preference would be to have both an environment variable and a configuration setting. I think
GH_UPDATE_CHECK<disabled | enabled>for the environment variable andupdate_check<disabled | enabled>for the configuration setting sound good. cc @ampinsk for design input.cc #743
mislav commentedon Oct 7, 2020
@danielfn Sorry for the nuisance! Agreed that there should be a way to disable the notifications. Furthermore, I think that update checks should never run in CI environments by default.
Closing as duplicate of #743 - follow that for updates!
mislav commentedon Oct 9, 2020
@danielfn From the next release, update checker will be automatically disabled in CI environments (detected by the presence of environment variables such as
CI) #2134danielfn commentedon Oct 10, 2020
@mislav Great! Thanks for the heads up :)