Skip to content

chore: update github pages for plugins - #2764

Merged
lizschwab merged 8 commits into
RaspberryPiFoundation:mainfrom
lizschwab:7767
Sep 10, 2026
Merged

lizschwab merged 8 commits into
RaspberryPiFoundation:mainfrom
lizschwab:7767

Conversation

@lizschwab

Copy link
Copy Markdown
Contributor

The details

Resolves

Fixes #7767

Proposed Changes

This updates the Blockly-Samples github pages to pull in the code from the core repo but still host on blockly-samples. There are no changes to how examples are hosted or built.

Reason for Changes

The plugins have moved to core, so we need to pull the code from there rather than from the stale and soon-to-be-deleted directory on the samples repo.

@lizschwab
lizschwab requested a review from a team as a code owner August 26, 2026 19:37
@lizschwab
lizschwab requested review from mikeharv and removed request for a team August 26, 2026 19:37
@lizschwab
lizschwab requested review from maribethb and removed request for mikeharv August 26, 2026 19:37
@lizschwab lizschwab assigned maribethb and unassigned mikeharv Aug 26, 2026
@lizschwab

Copy link
Copy Markdown
Contributor Author

Actions test run passed here: https://github.com/lizschwab/blockly-samples/actions/runs/33915266290

default: 'main'
type: string
core_branch:
description: 'Blockly core branch to publish from (for plugins)'

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.

I think with the way you're passing this in, it can also be a tag right? I think the default should be leaving this blank and having it use the latest published version of the plugins (so if the user didn't specify a branch/tag, you'd add a step finding the most recent git tag and use that as the checkout ref) because main may contain unreleased changes. but this could be a follow-up issue because this is really a feature request on top of this PR

Comment thread package.json Outdated
"deploy:prepare": "npm run deploy:prepare:plugins && npm run deploy:prepare:examples && gulp predeploy",
"deploy:prepare:examples": "npm install --workspace=examples && npm run prepare-examples && npm run predeploy --if-present --workspace=examples",
"deploy:prepare:plugins": "npm run clean && npm run build && lerna run predeploy --scope '@blockly/*'",
"deploy:prepare:plugins": "cd ../blockly && npx nx reset && lerna run clean --scope '@blockly/*' && lerna run build --scope '@blockly/*' && lerna run predeploy --scope '@blockly/*'",

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.

This is kind of sketchy to me because it presupposes that blockly is at ../blockly and there's no inherent reason that must be true (especially when running locally, but could also get out of sync if the workflow file ever changed the checkout location). I think these steps might belong in the workflow file itself for deploying on CI. and deploying locally might need some other solution

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Created an issue for the local side of this: #2766

Comment thread .github/workflows/update_gh_pages.yml Outdated
steps:
- name: Checkout
- name: Checkout Blockly-Samples
uses: actions/checkout@v3

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.

may be worth updating the version of the checkout command action while you're here, i think they're on 4 or 5 now

@lizschwab

Copy link
Copy Markdown
Contributor Author

@lizschwab
lizschwab requested a review from maribethb September 9, 2026 22:29
@lizschwab
lizschwab merged commit d27a967 into RaspberryPiFoundation:main Sep 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update github pages site on samples

3 participants