Trigger workflow of python packaging by Release
- Dominant language
- C++
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently Release triggers the following workflows:
* [Release](https://github.com/fixstars/ion-kit/actions/workflows/release.yml)
* [Upload Python Package](https://github.com/fixstars/ion-kit/actions/workflows/python_publish.yml)
However, `Upload Python Package` requires binaries built in `Release`, and it always fails once the job, requiring a manual re-run. In the worst case, the job remains in a failed status, and python package is not available.
The workflow should be `Release` -> `Upload Python Package`
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the workflow definitions linked in the issue, release.yml and python_publish.yml, and trace how Release currently starts both jobs. Verify the dependency between them and confirm that Upload Python Package waits for the Release artifacts before running and completes without a manual rerun.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100