You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the scheduled github action creates a git tag and pushes it to origin. Additionally, it does the same as the normal python-publish workflow (code is copy pasted). This is needed atm, because such a git tag is not a GitHub release. Therefore, the python-publish workflow would not be triggered.
It would be better to use the GitHub API to only create a full GitHub release. In this case GitHub would automatically trigger the existent python-publish workflow and we wouldn't need to have duplicate code in these actions.
An example of how you can create a release via the GitHub API is in the python-publish workflow where we push the new JSON-schemas.
Currently, the scheduled github action creates a git tag and pushes it to origin. Additionally, it does the same as the normal python-publish workflow (code is copy pasted). This is needed atm, because such a git tag is not a GitHub release. Therefore, the python-publish workflow would not be triggered.
It would be better to use the GitHub API to only create a full GitHub release. In this case GitHub would automatically trigger the existent python-publish workflow and we wouldn't need to have duplicate code in these actions.
An example of how you can create a release via the GitHub API is in the python-publish workflow where we push the new JSON-schemas.
BO4E-python/bo4e_schemas_create_release.py
Line 57 in 9995dce
The text was updated successfully, but these errors were encountered: