github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[PR #7094] [MERGED] [AI] Github action for unfreezing PRs #25546

New Issue
Closed
opened 2026-04-16 18:41:22 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 18:41:22 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/7094
Author: @MatissJanis
Created: 2/27/2026
Status: ✅ Merged
Merged: 2/28/2026
Merged by: @MatissJanis

Base: master ← Head: matiss/merge-freeze-unfreeze-action

📝 Commits (5)

  • ccba224 [AI] Add GitHub Action to add PR to Merge Freeze unblocked list when unfreeze label is added
  • 8a618e6 Rename 7093.md to 7094.md
  • c285550 Add concurrency control to unfreeze job in merge-freeze-unfreeze workflow
  • b23a69b Merge branch 'matiss/merge-freeze-unfreeze-action' of github.com:actualbudget/actual into matiss/merge-freeze-unfreeze-action
  • 68d9eb2 Refactor Merge Freeze workflow to simplify PR unblocking process

📊 Changes

2 files changed (+40 additions, -0 deletions)

View changed files

➕ .github/workflows/merge-freeze-unfreeze.yml (+34 -0)
➕ upcoming-release-notes/7094.md (+6 -0)

📄 Description

Description

Added a github action that unfreezes a PR if we add the "unfreeze" label to it. Slightly improving the ergonomics of this action.

Related issue(s)

N/A

Testing

Full disclosure: I have not tested this specific workflow. But I did test the CURL call locally and it worked as expected.

Checklist

  • Release notes added (see link above)
  • No obvious regressions in affected areas
  • Self-review has been performed - I understand what each change in the code does and why it is needed

🔄 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/7094 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 2/27/2026 **Status:** ✅ Merged **Merged:** 2/28/2026 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `matiss/merge-freeze-unfreeze-action` --- ### 📝 Commits (5) - [`ccba224`](https://github.com/actualbudget/actual/commit/ccba22434631d23a8719d5cd13e67ce84c31aa39) [AI] Add GitHub Action to add PR to Merge Freeze unblocked list when unfreeze label is added - [`8a618e6`](https://github.com/actualbudget/actual/commit/8a618e61d39932017981ba31cf0e3e8487e0e9a3) Rename 7093.md to 7094.md - [`c285550`](https://github.com/actualbudget/actual/commit/c2855500db874d88a8811fce36ef611057762b56) Add concurrency control to unfreeze job in merge-freeze-unfreeze workflow - [`b23a69b`](https://github.com/actualbudget/actual/commit/b23a69bf7b744e30b054067c908f6a72d8058100) Merge branch 'matiss/merge-freeze-unfreeze-action' of github.com:actualbudget/actual into matiss/merge-freeze-unfreeze-action - [`68d9eb2`](https://github.com/actualbudget/actual/commit/68d9eb2a778ae68f2c45a0da6cbf319ab6e3720b) Refactor Merge Freeze workflow to simplify PR unblocking process ### 📊 Changes **2 files changed** (+40 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/merge-freeze-unfreeze.yml` (+34 -0) ➕ `upcoming-release-notes/7094.md` (+6 -0) </details> ### 📄 Description <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> ## Description <!-- What does this PR do? Why is it needed? Please give context on the "why?": why do we need this change? What problem is it solving for you?--> Added a github action that unfreezes a PR if we add the "unfreeze" label to it. Slightly improving the ergonomics of this action. ## Related issue(s) <!-- e.g. Fixes #123, Relates to #456 --> N/A ## Testing <!-- What did you test? How can we reproduce the issue you are fixing or how can we test the feature you built? --> Full disclosure: I have not tested this specific workflow. But I did test the CURL call locally and it worked as expected. ## Checklist - [x] Release notes added (see link above) - [x] No obvious regressions in affected areas - [x] Self-review has been performed - I understand what each change in the code does and why it is needed <!--- actual-bot-sections ---> --- <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-04-16 18:41:22 -05: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#25546
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?