Skip to content

Let Embedder auto-detect applicable extras (zero configuration) #191

Description

@ineedjet

Context

The Embedder workflow currently requires callers to opt into optional
policies explicitly via the extra input, e.g.:

jobs:
  embedder:
    uses: rubykatzen/baseline/.github/workflows/embedder-shared.yml@v0.17.1
    with:
      extra: '["release-please"]'

If a repository already uses Release Please (a release-please-config.json,
.release-please-manifest.json, or the Release Please workflow present), the
caller still has to remember to add release-please to extra for Baseline
to check it.

Idea

Let the Embedder detect applicable extras automatically instead of requiring
every consumer to declare them by hand ("zero configuration"). For example,
if Release Please is already wired into the repository, Baseline could infer
and apply the release-please Embedder configuration without an explicit
extra: '["release-please"]' input.

Open questions

  • What signals indicate an extra applies (file presence, workflow content,
    something else), and how reliable are they across repositories?
  • Should auto-detection be the default with extra/skip still available to
    override it, or purely additive to what's explicitly declared?
  • Does this generalize to other optional Embedder configurations beyond
    release-please, or does each extra need its own detection rule?
  • How does auto-detection interact with the existing skip mechanism when a
    repository intentionally does not want a detected extra enforced?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    🚩Temporary fast-track flag

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions