Skip to content

[Copilot Dreaming] Remove an overbroad license-capture guarantee and clarify token alternatives - #25

Open
Copilot wants to merge 2 commits into
mainfrom
copilot/dream-curate-memories-20261112071723
Open

Copilot wants to merge 2 commits into
mainfrom
copilot/dream-curate-memories-20261112071723

Conversation

@Copilot

Copilot AI commented Nov 12, 2026 •

Copy link
Copy Markdown

🧠 How this helps Copilot

Copilot could assume that every complete license section in a package README appears in the generated notices. The extractor recognizes a narrower format. Removing the broader assurance helps Copilot avoid relying on unsupported license capture during release preparation.

Copilot could also add the dedicated token input to an existing environment-based authentication setup because the input table calls it required. That combination is rejected. Clarifying that the input supports explicit runs avoids implying it is the only supported route.

Review commit by commit for each change's rationale and evidence.

Note

Copilot Dreaming curates this repository's Copilot instructions and skills in the background, proposing updates to help agents work here. Learn more about Copilot Dreaming.

Automated details

Source: curate-memories Dream, analyzing main at 6e4c077.

Maintainers could assume a package's complete README license section was captured even when the extractor only accepts a license heading and two specific MIT text markers. Removing that broad assurance avoids treating the guide as evidence for unsupported extraction.
https://github.com/github/evals-action/blob/6e4c077e92194c7e75663d8d782426841047e887/tooling/license-notices.mjs#L48-L59

Unresolved entries still block public release and require authoritative terms and release-owner disposition.
https://github.com/github/evals-action/blob/6e4c077e92194c7e75663d8d782426841047e887/CONTRIBUTING.md#L80-L85

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Copilot
Copilot AI requested a review from a team as a code owner November 12, 2026 07:19
Copilot AI dynamic review requested due to automatic review settings November 12, 2026 07:19

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

The documentation-only change removes an unsupported README license-retention guarantee while preserving the surrounding generated-notice, provenance, and attribution guidance, leaving no active review issues.

No open issues 🎉

What changed in this PR

This documentation-only PR narrows contributor guidance to match the license extractor’s actual behavior, removing an unsupported guarantee that complete license sections from package READMEs are retained in generated notices.

Changes:

  • Removes the broad README license-capture guarantee.
  • Preserves the existing generated-notice, provenance, and attribution guidance.
File Description
CONTRIBUTING.md Removes the overbroad guarantee about retaining complete license sections from package READMEs while preserving the surrounding release guidance.

Review effort: Lite (auto)

Copilot could add the dedicated token input to an existing environment-based setup because the input table calls it required. The native environment builder accepts the explicit alias and rejects combining it with the dedicated input, so describing the input as supported rather than required avoids that mistaken prerequisite.
https://github.com/github/evals-action/blob/6e4c077e92194c7e75663d8d782426841047e887/src/native.ts#L56-L70

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Copilot Copilot AI changed the title [Copilot Dreaming] Remove an overbroad README license-capture guarantee [Copilot Dreaming] Remove an overbroad license-capture guarantee and clarify token alternatives Nov 12, 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.

3 participants