shad0w/pelagia-portal
1
0
Fork 0
Code Issues 6 Pull requests 1 Projects Releases 2 Packages Wiki Activity Actions

feat(staging): auto-refresh staging on every push to master #46

Merged
shad0w merged 2 commits from feat/staging-auto-refresh into master 2026-06-20 19:55:13 +00:00
Conversation 0 Commits 2 Files changed 3 +37 -2
shad0w commented 2026-06-20 19:38:11 +00:00
Owner
Copy link

Staging now tracks master automatically.

  • .forgejo/workflows/staging.yml runs on every push to master (every merged PR) on the host runner, rebuilding ppms-staging (port 3200) to the latest master via staging-up.sh. Concurrency-coalesced (newest master wins); also workflow_dispatch for on-demand runs.
  • staging-up.sh: drop --update-env and unset FORGEJO_* so the runner's ephemeral token can't leak into the staging process (same class of bug as the prod deploy fix in #43).

Staging runs pnpm dev, so "rebuild" = checkout latest + restart (the dev server recompiles) — no full prod build. Automation/CI only.

Note: this self-activates on the first master push after it merges.

Staging now tracks master automatically. - `.forgejo/workflows/staging.yml` runs on **every push to master** (every merged PR) on the host runner, rebuilding `ppms-staging` (port 3200) to the latest master via `staging-up.sh`. Concurrency-coalesced (newest master wins); also `workflow_dispatch` for on-demand runs. - `staging-up.sh`: drop `--update-env` and unset `FORGEJO_*` so the runner's ephemeral token can't leak into the staging process (same class of bug as the prod deploy fix in #43). Staging runs `pnpm dev`, so "rebuild" = checkout latest + restart (the dev server recompiles) — no full prod build. Automation/CI only. Note: this self-activates on the first master push after it merges.
shad0w added 1 commit 2026-06-20 19:38:11 +00:00
feat(staging): auto-refresh staging on every push to master
All checks were successful
PR checks / checks (pull_request) Successful in 30s
Details
9f8297aa7e 
New .forgejo/workflows/staging.yml rebuilds ppms-staging to latest master on every
merge (push to master) on the host runner, so staging always mirrors the trunk;
concurrency-coalesced + workflow_dispatch. Also drops --update-env from staging-up.sh
(and unsets FORGEJO_*) so the runner's ephemeral token can't leak into ppms-staging.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
shad0w added 1 commit 2026-06-20 19:39:48 +00:00
Merge branch 'master' into feat/staging-auto-refresh
All checks were successful
PR checks / checks (pull_request) Successful in 30s
Details
a0c6ccba3c
shad0w merged commit 64fefd15a8 into master 2026-06-20 19:55:13 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is broken

  
claude-failed

Automated fix attempt failed

  
claude-pr

Claude opened a PR for this

  
claude-queue

Queued for automated Claude fix

  
claude-working

Claude is working on this

  
feature

New functionality

  
interactive

Run with Claude interactively/steered � not safe for the unattended watcher

  
portal

Reported via portal Report Issue button

  
triaged

Triage has run on this portal issue (prevents re-triage)

No labels
bug
claude-failed
claude-pr
claude-queue
claude-working
feature
interactive
portal
triaged
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: shad0w/pelagia-portal#46
No description provided.
Delete branch "feat/staging-auto-refresh"

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?