[PR #561] [MERGED] fix(ci): Trigger Binary workflow on workflow_run, workflow_dispatch. #9229

New issue

Closed

opened 2026-05-23 03:56:00 +01:00 by JakeStanger · 0 comments

JakeStanger commented

2026-05-23 03:56:00 +01:00

Owner

📋 Pull Request Information

Original PR: https://github.com/JakeStanger/ironbar/pull/561
Author: @slowsage
Created: 4/29/2024
Status: ✅ Merged
Merged: 4/29/2024
Merged by: @JakeStanger

Base: master ← Head: fix/workflow_run

📝 Commits (1)

4e9dfc1 fix(ci): Trigger Binary workflow on workflow_run, workflow_dispatch.

📊 Changes

1 file changed (+32 additions, -3 deletions)

View changed files

📝 .github/workflows/binary.yml (+32 -3)

📄 Description

Please check the releases and actions log on fork's master branch to verify. Master is ahead of this commit.
Was pretty easy to add check and handle failures:
Here is the order of Binary runs in actions log.

Deploy => binary succeeds. assets uploaded to v0.15.1
Deploy and binary failed.
workflow_dispatch - succeeds, uploads to v0.15.2
Manual release. succeeds, uploads to v0.15.3

Edit: The basic idea is to keep deploy.yml independent and bind to last release ref manually which automatically enabled workflow_dispatch.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/JakeStanger/ironbar/pull/561 **Author:** [@slowsage](https://github.com/slowsage) **Created:** 4/29/2024 **Status:** ✅ Merged **Merged:** 4/29/2024 **Merged by:** [@JakeStanger](https://github.com/JakeStanger) **Base:** `master` ← **Head:** `fix/workflow_run` --- ### 📝 Commits (1) - [`4e9dfc1`](https://github.com/JakeStanger/ironbar/commit/4e9dfc10cc799f14c119ecdfa9dc02139ee57f78) fix(ci): Trigger Binary workflow on workflow_run, workflow_dispatch. ### 📊 Changes **1 file changed** (+32 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/binary.yml` (+32 -3) </details> ### 📄 Description Please check the [releases](https://github.com/slowsage/ironbar/releases) and [actions](https://github.com/slowsage/ironbar/actions) log on fork's master branch to verify. [Master](https://github.com/slowsage/ironbar/commits/master/) is ahead of this commit. Was pretty easy to add check and handle failures: Here is the order of Binary runs in [actions](https://github.com/slowsage/ironbar/actions) log. 1. Deploy => binary succeeds. assets uploaded to v0.15.1 2. Deploy and binary failed. 3. workflow_dispatch - succeeds, uploads to v0.15.2 4. Manual release. succeeds, uploads to v0.15.3 Edit: The basic idea is to keep deploy.yml independent and bind to last release ref manually which automatically enabled `workflow_dispatch`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

JakeStanger

2026-05-23 03:56:00 +01:00