Skip to content

fix(ci): check out the devkit in upstream-compat, not just the plugin #61

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
omar-nahhas merged 1 commit into from
Aug 5, 2026
Merged

fix(ci): check out the devkit in upstream-compat, not just the plugin #61

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
11 changes: 11 additions & 0 deletions .github/workflows/upstream-compat.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,17 @@ jobs:
permissions:
contents: read
steps:
# The devkit itself must land at the workspace ROOT: the harness build below
# references devcontainer/Containerfile relative to it. The first version of
# this job checked out only the plugin and every leg died with
# `context must be a directory: .../devcontainer` — the devkit was simply
# never fetched.
#
# Order matters. A checkout without `path` cleans the workspace, so it has to
# run BEFORE the plugin is placed in plugin/, or it would delete it.
- name: Checkout the devkit (harness + scripts)
uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4

- name: Checkout the plugin under test
uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
with:
Expand Down
Loading