github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 20:23:07 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #5586] [MERGED] Dispatch github ci jobs after running update-vrt workflow #6012

New Issue
Closed
opened 2026-02-28 21:22:31 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:22:31 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/5586
Author: @MatissJanis
Created: 8/20/2025
Status: ✅ Merged
Merged: 8/20/2025
Merged by: @MatissJanis

Base: master ← Head: matiss/vrt-update-commit

📝 Commits (2)

  • b8e3786 Enhance CI workflows to support repository dispatch events and improve branch handling
  • b2cd0a5 Add release notes for PR #5586

📊 Changes

5 files changed (+47 additions, -3 deletions)

View changed files

📝 .github/workflows/build.yml (+11 -1)
📝 .github/workflows/check.yml (+13 -1)
📝 .github/workflows/codeql.yml (+5 -1)
📝 .github/workflows/update-vrt.yml (+11 -0)
➕ upcoming-release-notes/5586.md (+7 -0)

📄 Description

Enhance CI workflows to support repository dispatch events and improve branch handling

  • Added support for repository_dispatch events in build, check, and codeql workflows.
  • Updated concurrency group to include client_payload.pr_number for better context.
  • Modified checkout steps to reference the correct branch from client_payload if available.

Important: I have not actually fully tested this. In theory - I think it will work. But if it fails after merging (because we need to merge to test it.. and I'm a bit lazy in terms of creating a fork and all that stuff..) - I will simply roll back this PR.

🔄 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/actualbudget/actual/pull/5586 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 8/20/2025 **Status:** ✅ Merged **Merged:** 8/20/2025 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `matiss/vrt-update-commit` --- ### 📝 Commits (2) - [`b8e3786`](https://github.com/actualbudget/actual/commit/b8e3786f76d015454e8f5b9a706b64b07308ca39) Enhance CI workflows to support repository dispatch events and improve branch handling - [`b2cd0a5`](https://github.com/actualbudget/actual/commit/b2cd0a54b74278d5e6df4f679860f3afb92faaea) Add release notes for PR #5586 ### 📊 Changes **5 files changed** (+47 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build.yml` (+11 -1) 📝 `.github/workflows/check.yml` (+13 -1) 📝 `.github/workflows/codeql.yml` (+5 -1) 📝 `.github/workflows/update-vrt.yml` (+11 -0) ➕ `upcoming-release-notes/5586.md` (+7 -0) </details> ### 📄 Description Enhance CI workflows to support repository dispatch events and improve branch handling - Added support for `repository_dispatch` events in build, check, and codeql workflows. - Updated concurrency group to include `client_payload.pr_number` for better context. - Modified checkout steps to reference the correct branch from `client_payload` if available. **Important:** I have not actually fully tested this. In theory - I think it will work. But if it fails after merging (because we need to merge to test it.. and I'm a bit lazy in terms of creating a fork and all that stuff..) - I will simply roll back this PR. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 21:22:32 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#6012
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?