Skip to content

ci: reject unknown keys in slice definition files #1186

Description

@lczyk

Chisel ignores keys it doesn't recognise for forwards-compatibility reasons. This however means that a misspelled key is indistinguishable from a future key, and chisel-releases ci is the right place to try to catch it. We should add such a ci.

Specific example which just happened: Several copyright slices used content: instead of contents: and silently shipped no copyright. This is now fixed / in-flight:

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions