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 #6753] [MERGED] Fix edge nightly deploy #21078

New Issue
Closed
opened 2026-04-14 21:53:11 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-14 21:53:11 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/6753
Author: @MikesGlitch
Created: 1/22/2026
Status: ✅ Merged
Merged: 1/22/2026
Merged by: @MikesGlitch

Base: master ← Head: fix-edge-nightly

📝 Commits (8)

📊 Changes

3 files changed (+52 additions, -46 deletions)

View changed files

➖ .github/workflows/edge-release.yml (+0 -46)
➕ .github/workflows/publish-nightly-edge.yml (+46 -0)
➕ upcoming-release-notes/6753.md (+6 -0)

📄 Description

Only able to test this once it's merged to master.

Deployments on edge need to remain locked so we can keep our previews without it deploying on every merge to master.

Previously we were attempting to force a publish through via CI - that didn't work.

This restore API call seems to bypass the lock when I run it locally.

🔄 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/6753 **Author:** [@MikesGlitch](https://github.com/MikesGlitch) **Created:** 1/22/2026 **Status:** ✅ Merged **Merged:** 1/22/2026 **Merged by:** [@MikesGlitch](https://github.com/MikesGlitch) **Base:** `master` ← **Head:** `fix-edge-nightly` --- ### 📝 Commits (8) - [`aefd044`](https://github.com/actualbudget/actual/commit/aefd044f9bfd98afc21962840c83a360548b7308) fix edge nightly deploy - [`29a0f7c`](https://github.com/actualbudget/actual/commit/29a0f7cc0d9a1a0a2621d0e0d7c91d0370189406) fix name - [`3d42559`](https://github.com/actualbudget/actual/commit/3d4255914ee9157b55f1b479f4add8deda736127) rename file - [`081d832`](https://github.com/actualbudget/actual/commit/081d832b53d9a105a387e4ff57874e1ecad78344) clarifying comment - [`35f8247`](https://github.com/actualbudget/actual/commit/35f8247ed32cc71cd8c7ef7eba6cd5b8a3c35292) bit more clear - [`02e52eb`](https://github.com/actualbudget/actual/commit/02e52eb0f68ce37f8614a67c636427fc5d1d71a0) Merge branch 'master' of https://github.com/MikesGlitch/actual into fix-edge-nightly - [`38b3633`](https://github.com/actualbudget/actual/commit/38b3633adfb52c170b764b196864c69fc649d7bc) adding release notes to satisfy pipeline - [`110667c`](https://github.com/actualbudget/actual/commit/110667c665d6db3429aee9059b3ff76fa9b70d2e) spelling ### 📊 Changes **3 files changed** (+52 additions, -46 deletions) <details> <summary>View changed files</summary> ➖ `.github/workflows/edge-release.yml` (+0 -46) ➕ `.github/workflows/publish-nightly-edge.yml` (+46 -0) ➕ `upcoming-release-notes/6753.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. --> Only able to test this once it's merged to master. Deployments on edge need to remain locked so we can keep our previews without it deploying on every merge to master. Previously we were attempting to force a publish through via CI - that didn't work. This restore API call seems to bypass the lock when I run it locally. --- <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-14 21:53:11 -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#21078
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?