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
The current action sets the BASE_SHA to HEAD~1 if it cannot find a successful workflow run. In my specific case, I created a monorepo and checked-in several commits before I got something that could be built successfully.
It would be great if I could either configure this action to use the first commit as the BASE_SHA or specify a default BASE_SHA myself.
Would this be possible?
The text was updated successfully, but these errors were encountered:
An alternative might be to also set an environment variable, say LAST_SUCCESSFUL_WORKFLOW_FOUND, to either yes or no (or true/false). We could then use this to reset the BASE_SHA environment variable to whatever SHA we wanted under these conditions.
This would be useful also in use case where the 2nd workflow(triggered by workflow_dispatch from 1st workflow) want to check the affected projects from the previous workflow. Currently 2nd workflow always see same sha for both env.
Instead of fallback_sha, can we have base_sha?
The current action sets the
BASE_SHA
toHEAD~1
if it cannot find a successful workflow run. In my specific case, I created a monorepo and checked-in several commits before I got something that could be built successfully.It would be great if I could either configure this action to use the first commit as the
BASE_SHA
or specify a defaultBASE_SHA
myself.Would this be possible?
The text was updated successfully, but these errors were encountered: