Skip to content

source.json should be a source.yaml, just for consistency #19

@christoph-jerolimov

Description

@christoph-jerolimov

PRs like this:

creates a source.json (manually formatted for readability) like this:

{
  "repo": "https://github.com/backstage/community-plugins",
  "repo-ref": "335037a9f57eef5a989363cb9779cfaeb8c81f9b",
  "repo-flat": false
}

Since everything in the Backstage world is using YAMLs, and also the PR creates a plugins-list.yaml I would recommend to create a source.yaml as well

repo: "https://github.com/backstage/community-plugins"
repo-ref: "335037a9f57eef5a989363cb9779cfaeb8c81f9b"
repo-flat: false

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions