Currently the automated continuous integration workflow is not accessing secrets for pull requests when they are opened. This causes the CI tests to fail as the environment variables stored as secrets are required for successfully running and passing the automated tests. This can be misleading if the changes in the pull requests are not failing the same CI workflow tests in the development branches.
This pull request aims to try and fix this issue.
Related Issue
Solves #42
Type of change
[x] Bug fix
How Has This Been Tested?
It is not possible to test given the resources available. To test this requires merging it to the master and then re-running the CI worjflows for all other existing pull requests.
Checklist:
[x] Does a similar (open or closed) pull request not already exist?
[x] Is the pull request head repository a fork repository?
[x] Is the pull request compare branch a development branch?
[x] Is the code documented, particularly in hard-to-understand areas?
[x] Does the code build without new warnings?
[x] Has a self- and/or peer-review of the code been performed?
[x] Does all new and existing automated testing pass?
[x] Is the person responsible for the repository assigned to the pull request?
Description
Currently the automated continuous integration workflow is not accessing secrets for pull requests when they are opened. This causes the CI tests to fail as the environment variables stored as secrets are required for successfully running and passing the automated tests. This can be misleading if the changes in the pull requests are not failing the same CI workflow tests in the development branches.
This pull request aims to try and fix this issue.
Related Issue
Solves #42
Type of change
How Has This Been Tested?
It is not possible to test given the resources available. To test this requires merging it to the master and then re-running the CI worjflows for all other existing pull requests.
Checklist: