Open ehennestad opened 8 months ago
Following up on this:
"Module" repositories, i.e openMINDS_core
provides some inputs (branch name, repository name) to the build
action of openMINDS/pipeline
.
The build
action uses these inputs to create a commit message like this:
build triggered by submodule openMetadataInitiative/openMINDS_stimulation version v1
However, these input arguments are not propagated to any of the target repositories' build
action (and I don't know if that is possible), but all the target repositories have the same command for pushing in their build
action, i.e:
git commit -m "build triggered by submodule ${{ inputs.repository }} version ${{ inputs.branch }}"
@olinux can we have a look at this together?
The build workflows of the target repositories have the following code for creating a commit message:
However the
inputs.repository
andinputs.branch
variables are not added to the actual commit message, see for example : https://github.com/openMetadataInitiative/openMINDS_JSON-Schema/commit/2628169cc48eaa69a020a93f9e9463e59d409077