Skip to content

Stricter CI check to catch common mistakes early on #73

Open

Description

@adamziel
  • Confirm the metadata field exists in the Blueprint place
  • Confirm it's not a direct copy of another Blueprint from the repo – people often copy&paste those and merging such a PR would lead to a Gallery entry that looks like a duplicate
  • Confirm the author field is the same as the PR opener's GitHub username

cc @bgrgicak would you be able to help with that?

Activity

  1. moved this from Inbox to Up next in Playground Boardon Oct 25, 2024
  2. self-assigned this
    on Oct 28, 2024
  3. removed their assignment
    on Jun 18, 2025
  4. nadeem-khan commented on Oct 23, 2026

    @nadeem-khan

    Hi maintainers! 👋

    I'd like to work on this issue as my first contribution to the WordPress Blueprints project.

    I'm interested in improving the CI validation checks, particularly adding validation for missing required metadata in Blueprint files.

    Would it be okay to tackle this as a small, focused PR rather than implementing all the checks at once?

    Also, is this issue still available for contribution?

    Thanks!

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

    No labels
    No labels

    Type

    No type

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions