Adjust cancel-workflow-on-failure defaults (OSOE-571)

[0liver]

Adjust the default value of the cancel-workflow-on-failure workflow parameter based on the usual usage.

We can set it to false for publish-nuget, for example, which is a reusable workflow that will usually be used alone, not as one job among many in a larger workflow (where the workflow cancellation matters). For such workflows, it could even be the default, as well as for create-jira-issues-for-community-activities and validate-submodule-pull-request and validate-pull-request. Check all the existing workflows though.

https://github.com/Lombiq/Open-source-template should also be updated.

Jira issue

[BenedekFarkas]

It does cancel other workflows' jobs too, isn't it? In that case it's just a matter of updating the name and maybe adding a description.

[0liver]

It does cancel other workflows' jobs too, isn't it?

Oh, right! I overlooked that. I guess, then we don't need to change it (although I agree that it could be named slightly more clearly).

[Piedone]

What name would make it clearer for you?

[0liver]

Tbh, looking at this again, I see now that the actions I've referred to will most often be used as part of a larger workflow. Somehow, I missed that.

So I guess, the improvement we could make is setting cancel-workflow-on-failure to false in workflows that contain only a single action. That would help with the status badge on the actions overview page.

[BenedekFarkas]

I think changing that would be problematic if multiple workflows are triggered at the same time (or if that's not the case now, you'd need to remember that when adding a new workflow).

[0liver]

I don't quite understand.

[Piedone]

We can set it to false for publish-nuget, for example, yes, which is a reusable workflow that will usually be used alone, not as one job among many in a larger workflow (where the workflow cancellation matters). For such workflows, it could even be the default, as well as for create-jira-issues-for-community-activities and validate-submodule-pull-request and validate-pull-request.

[0liver]

Do you still deem this important enough to tackle? If yes, we should adjust the title here and in JIRA.

[Piedone]

Updated.

[Piedone]

Once done, the "Saving on computing resources" docs section will need to be adjusted too.