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
Don't use git commit sha for the CIRRUS_LAST_GREEN_CHANGE env variable if [skip ci] option was used.
Context
Right now it's possible to work around the failed build by just updating e.g. README.md, and setting [skip ci] in the commit message. This breaks setups that use the CIRRUS_LAST_GREEN_CHANGE env to e.g. lint only changed files, or in case the suite is skipped completely if there are no changes to some specific files.
The text was updated successfully, but these errors were encountered:
Description
Don't use git commit sha for the
CIRRUS_LAST_GREEN_CHANGE
env variable if[skip ci]
option was used.Context
Right now it's possible to work around the failed build by just updating e.g.
README.md
, and setting[skip ci]
in the commit message. This breaks setups that use theCIRRUS_LAST_GREEN_CHANGE
env to e.g. lint only changed files, or in case the suite is skipped completely if there are no changes to some specific files.The text was updated successfully, but these errors were encountered: