Option to consider different workflow states as successful

[joh-klein]

We have the following situation: our workflow waits at the very end for approval of the production environment deployment. This only happens occasionally. Thus only then are these workflows considered successful and used as base.

- name: Derive appropriate SHAs for base and head for `nx affected` commands
  uses: nrwl/nx-set-shas@v4
  with:
    # The state to check for
    #
    # Default: success
    last-successful-state: "success,waiting"

[mandarini]

Hi there @joh-klein ! Thank you for the feature request. You can try submitting a PR if you want, and I can review it! Otherwise, I will try to take a look at the request and see if I have time some time in the next month!

[DorSharonGoPerfect]

This is actually a feature we badly need.
Any chance of considering implementing it?

[JamesHenry]

@joh-klein I see you forked the action and added this functionality for yourself. Would you like to open a PR back to this repo and we can get it added?

The only change I would request is that you go for last-successful-status not "state", to match the GitHub property.

[JamesHenry]

I would please also include an example of your use-case in the README and why you might want to ever override this property