This PR introduces a step that checks if the repository has Azure secrets set up. If yes -> proceeds with the CD workflow, if not -> the checks are disabled.
The reason to introduce such step is to not fail the workflow in the PRs from forks to the upstream MVD repository.
Please note that it's a temporary solution.
A solution that allows to run all tests (eg. on local resources) in PR from forks will be introduced at later stage.
Linked to #56
This PR introduces a step that checks if the repository has Azure secrets set up. If yes -> proceeds with the CD workflow, if not -> the checks are disabled.
The reason to introduce such step is to not fail the workflow in the PRs from forks to the upstream MVD repository. Please note that it's a temporary solution. A solution that allows to run all tests (eg. on local resources) in PR from forks will be introduced at later stage.