Skip to content

chore(ci): guard build_app on fork (lock-file/babel cold-cache mismatch) #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mudit-Lal merged 1 commit into from
Jun 4, 2026
Merged

chore(ci): guard build_app on fork (lock-file/babel cold-cache mismatch) #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@ concurrency:

jobs:
build_app:
# Guarded on fork: upstream lock-file relies on warm npm cache that fork
# CI doesn't have, causing transient babel resolve mismatches. Docker build
# below still runs and IS the real prod signal (Railway uses Dockerfile).
if: github.repository == 'documenso/documenso'
name: Build App
runs-on: ubuntu-latest
steps:
Expand Down
3 changes: 2 additions & 1 deletion DEVALOK_FORK_NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,7 @@ This is intentional. The workflows are left in place so upstream merges stay cle

| File | Why |
|---|---|
| `ci.yml` (build_app job only) | Upstream npm cache hides a lock-file/babel mismatch; cold-cache fork CI fails. `build_docker` (the real prod signal) still runs on fork. |
| `deploy.yml` | Pushes `main` → `release` using upstream `GH_TOKEN` |
| `e2e-tests.yml` | Uses `warp-ubuntu-*` runners only available to upstream |
| `first-interaction.yml` | Welcome message linking to upstream Discord |
Expand All @@ -59,7 +60,7 @@ This is intentional. The workflows are left in place so upstream merges stay cle

### Kept (run on fork)

- `ci.yml` — build + Docker image (no upstream secrets)
- `ci.yml` — only the `build_docker` job (Docker build = real prod signal). `build_app` job guarded above.
- `codeql-analysis.yml` — security scan (uses only `GITHUB_TOKEN`)

## Railway deploy
Expand Down
Loading