If there are no changed files (e.g. tagging or similar operation), the masesgroup/retrieve-changed-files@v2 action throws an error and aborts the workflow. The latter is fine, but the former results in a notification that the workflow failed.
It would be nice if we could somehow indicate that this particular "failure" is actually okay and terminate without generating the notification. But on a short perusal of the GH documentation, it is not clear how this might be achieved.
If there are no changed files (e.g. tagging or similar operation), the masesgroup/retrieve-changed-files@v2 action throws an error and aborts the workflow. The latter is fine, but the former results in a notification that the workflow failed.
It would be nice if we could somehow indicate that this particular "failure" is actually okay and terminate without generating the notification. But on a short perusal of the GH documentation, it is not clear how this might be achieved.