We have moved the functional code for the workflows to the organization .github repository to be called as reusable workflows. This allows us to reduce the amount of locations code needs to be modified for workflow changes.
What was the solution? (How)
Remove reuse_python_build.yml since this is now stored in the .github repository
Change the bump, publish, code quality, integration test workflows to call the reusable workflows in the .github repository
What is the impact of this change?
workflows in this repository now call reusable repositories from the .gihtub repository
How was this change tested?
Tested in a development org and repository
Was this change documented?
no
Is this a breaking change?
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
What was the problem/requirement? (What/Why)
We have moved the functional code for the workflows to the organization .github repository to be called as reusable workflows. This allows us to reduce the amount of locations code needs to be modified for workflow changes.
What was the solution? (How)
What is the impact of this change?
workflows in this repository now call reusable repositories from the .gihtub repository
How was this change tested?
Tested in a development org and repository
Was this change documented?
no
Is this a breaking change?
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.