Skip to content

DO NOT MERGE: test replacement-PR behaviour in generate_notebooks.yml - #102

Closed
ablaom wants to merge 2 commits into
devfrom
abandon-evans
Closed

ablaom wants to merge 2 commits into
devfrom
abandon-evans

Conversation

@ablaom

@ablaom ablaom commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Test PR — do not merge.

Exercises the reworked generate_notebooks.yml, which no longer uses
peter-evans/create-pull-request. That action rebases only the changes made
during the workflow onto base, which dropped the parent PR's own commits
from the spawned PR.

What to check on the spawned "Commit Notebook Markdown Changes" PR:

  • it contains the commits of this PR (the workflow change and the DUMMY
    notebook.jl edit), not just the regenerated markdown
  • it contains the regenerated notebook.md on top
  • its body's preview link has a real PR number substituted in, not a blank

Includes a deliberate DUMMY commit to UsingMLJ/01_basics/notebook.jl purely
to trigger regeneration.

ablaom and others added 2 commits October 17, 2026 21:10
peter-evans/create-pull-request rebases only the changes made during the
workflow onto `base` whenever `base` differs from the checked-out ref, so
the spawned PR contained the generated markdown but none of the parent
PR's own commits.

Build the branch directly instead: for a pull_request event the checkout
is the merge commit, so branching from HEAD and committing the generated
files gives a branch that diffs against the base as "parent's changes +
generated files". Create/update the PR with gh.

Also add an explicit permissions block, now that the job pushes directly.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Attention

A notebook or Project.toml file has changed and new notebook markdown has been generated. Review #103, which replaces the current PR, to commit the changes and update the documentation on gh-pages.
This PR can be CLOSED at any time.

@ablaom ablaom closed this Oct 17, 2026
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.

1 participant