Add possibility to release without running any tests

[flomnes]

This is useful for releases where we know results will deviate from reference results.

Currently

Workflow when results change

1. Disable tests by commenting them in the YML workflows
2. Create a RC release
3. Generate new reference results
4. Uncomment tests in YML workflows
5. Create a definitive release with tests

Workflow when results don't change

1. Generate new release with tests

After

Workflow when results change

1. Create release without running the tests
2. Create a RC release
3. Generate new reference results
4. Generate definitive release with tests

We save two steps (comment/uncomment).

Workflow when results don't change

1. Generate new release with tests

Note

It won't be possible to manually create a new release, all releases will have to be created using the new_release.yml workflow. This is because the condition for asset upload changes from ${{ github.event_name == 'release' && github.event.action == 'created' }} to ${{ github.event_name == 'workflow_call' }}.

Reference

https://docs.github.com/en/actions/using-workflows/reusing-workflows
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callinputsinput_idtype

[watermelon-copilot-for-code-review]

Watermelon AI Summary

AI Summary deactivated by flomnes

GitHub PRs

• #1852 - Add possibility to release without running any tests - By flomnes 1 days ago

• #739 - preparing loop around benders solver - By a-zakir 23 hours ago

• #1865 - fix(xpansion): update for improved parameter handling and code refactoring - By MartinBelthle 2 weeks ago

Antares_Simulator is an open repo and Watermelon will serve it for free.
🍉🫶
Have you starred Watermelon?

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud