Ok we made a slight blunder in putting all the actions in the normal .github/workflows directory because it means that the actions attempt to run on this repo itself.
Slightly not ideal for a variety of reasons.
Obvious solution:
We only need workflows in .github/workflows if they are going to apply to this repo anyway, otherwise the actions are being referenced externally by way of uses jobs. Thus, lets just re-arrange the repo.
Move the existing Workflows out to more generic topic levels, not team specific per-se but more general topics.
./.github/workflows/pre-commit.yml
./.github/workflows/produce_data.yml
./.github/workflows/test_job_id.yml
./.github/check-spdx.yml
./.pre-commit-config.yaml
./.pre-commit-config.yaml.swp
./Readme.md
./.gitignore
./LICENSE
./community/on-community-issue.yml
./data_collection/action.yml
./data_collection/download_workflow_data.sh
./data_collection/pytest.ini
./data_collection/Readme.md
./data_collection/requirements.txt
./data_collection/sftp-cicd.txt
./data_collection/sftp-optest.txt
./data_collection/sftp-perf.txt
./data_collection/src/cicd.py
./data_collection/src/optests.py
./data_collection/src/parsers/junit_xml_utils.py
./data_collection/src/parsers/parser.py
./data_collection/src/parsers/python_pytest_parser.py
./data_collection/src/parsers/python_unittest_parser.py
./data_collection/src/parsers/tt_torch_model_tests_parser.py
./data_collection/src/pydantic_models.py
./data_collection/src/shared.py
./data_collection/src/test_parser.py
./data_collection/src/benchmark.py
./data_collection/src/generate_data.py
./data_collection/src/utils.py
./data_collection/test/data/11236784732/artifacts/test-reports-runner/report_31237673766.xml
[...]
./data_collection/test_collect_data_action.yml
./job_helpers/job_id/Readme.md
./job_helpers/job_id/action.yml
./job_helpers/maximize_space/Readme.md
./job_helpers/maximize_space/action.yml
./job_helpers/maximize_space/test_maximize_space.yml
(exact breakup discussion is basically this bug, the above is mostly something to argue from, not an exact it should be this way)
Vague thinking is mostly:
//<everything for that item goes in this directory so it's semi-self contained>
if we want to run the action from the repo itself, just make it's own uses in the main .github/workflows/ that references it and calls it a day?
Thoughts? @vmilosevic specifically
Ok we made a slight blunder in putting all the actions in the normal .github/workflows directory because it means that the actions attempt to run on this repo itself.
Slightly not ideal for a variety of reasons.
Obvious solution:
We only need workflows in .github/workflows if they are going to apply to this repo anyway, otherwise the actions are being referenced externally by way of
usesjobs. Thus, lets just re-arrange the repo.Move the existing Workflows out to more generic topic levels, not team specific per-se but more general topics.
(exact breakup discussion is basically this bug, the above is mostly something to argue from, not an exact it should be this way)
Vague thinking is mostly:
//<everything for that item goes in this directory so it's semi-self contained>
if we want to run the action from the repo itself, just make it's own
usesin the main .github/workflows/ that references it and calls it a day?Thoughts? @vmilosevic specifically