Skip to content

Run roam, obsidian and database workflows when content-model changes #1520

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

Open
MarkAlex1234 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Run roam, obsidian and database workflows when content-model changes #1520

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
1 change: 1 addition & 0 deletions .github/workflows/obsidian-main.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ on:
paths:
- "apps/obsidian/**"
- "packages/database/**"
- "packages/content-model/**"

@devin-ai-integration devin-ai-integration Bot Oct 5, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Shared-package releases lose Linear tracking

For content-model-only pushes, obsidian-main publishes a beta without including the change in its Linear release. Its include_paths still excludes content-model; roam-main likewise excludes content-model and types after deploying them.

Learn more

The new push filters cause main-branch changes in shared packages to publish or deploy. The subsequent Linear syncs use separate path lists, which still exclude those packages in the Obsidian sync and the Roam sync. A change with no other matching paths therefore ships without its corresponding Linear release entry. The manual stable-release workflows reuse those older lists too.

Example: A merged PR changes only packages/content-model/src/schema/index.ts. Both main workflows run, but neither Linear sync includes that path, so the published builds lack that PR in their Linear release tracking.

Recommended fix: Add packages/content-model/** to Obsidian's Linear include_paths, and add both packages/content-model/** and packages/types/** to Roam's. Update the corresponding manual stable-release syncs to use the same paths.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

- "packages/utils/**"

permissions:
Expand Down
2 changes: 2 additions & 0 deletions .github/workflows/roam-main.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ on:
- "packages/tailwind-config/**"
- "packages/utils/**"
- "packages/database/**"
- "packages/content-model/**"
- "packages/types/**"
- "packages/ui/**"

env:
Expand Down
2 changes: 2 additions & 0 deletions .github/workflows/roam-pr.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ on:
- "packages/tailwind-config/**"
- "packages/utils/**"
- "packages/database/**"
- "packages/content-model/**"
- "packages/types/**"
- "packages/ui/**"
env:
BLOB_READ_WRITE_TOKEN: ${{ secrets.BLOB_READ_WRITE_TOKEN }}
Expand Down
2 changes: 2 additions & 0 deletions .github/workflows/test-database.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ on:
pull_request:
paths:
- "packages/database/**"
- "packages/content-model/**"
- "packages/utils/**"
env:
SUPABASE_USE_DB: local
SUPABASE_PROJECT_ID: test
Expand Down