Skip to content

license-note: Make the routine step opt-in - #70

Merged
schloerke merged 1 commit into
mainfrom
schloerke/license-note-opt-in
Aug 17, 2026
Merged

schloerke merged 1 commit into
mainfrom
schloerke/license-note-opt-in

Conversation

@schloerke

Copy link
Copy Markdown
Collaborator

Follow-up to #69: defaults the license-note input to false.

The marker check already meant the step did nothing in a repo that had not opted in — no markers, no work. But that left the opt-in implicit and one-sided: a repo that happens to have a LICENSE.note with matching markers would start getting auto-commits and PR comments purely because v1 moved. Turning something on for a consumer without them asking is the wrong default for this repo's @v1 model.

Opting in is now explicit on both ends:

jobs:
  routine:
    uses: rstudio/shiny-workflows/.github/workflows/routine.yaml@v1
    with:
      license-note: true

plus the marker pair in LICENSE.note.

No behavior change for anyone who has not opted in, since the step was already a no-op for them. Docs updated in both READMEs.

rstudio/shiny#4426 is updated to pass license-note: true.

Defaults `license-note` to false. The marker check already meant the step
did nothing in a repo that had not opted in, but a repo that happens to
have a LICENSE.note with matching markers should not start getting
auto-commits and PR comments just because `v1` moved.

Opting in is now explicit on both ends: `license-note: true` in the caller
workflow, and the markers in the file.
@schloerke
schloerke merged commit 0e822fc into main Aug 17, 2026
@schloerke
schloerke deleted the schloerke/license-note-opt-in branch August 17, 2026 15:59
schloerke added a commit to rstudio/shiny that referenced this pull request Aug 17, 2026
rstudio/shiny-workflows#70 made the step opt-in, defaulting to false, so
the markers in LICENSE.note are not enough on their own any more.
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