Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document which krefs set bugtracker, release_date, and metanetkan #3519

Merged
merged 1 commit into from
Jan 20, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions Spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -741,8 +741,10 @@ When used, the following fields will be auto-filled if not already present:
- `resources.homepage`
- `resources.spacedock`
- `resources.repository`
- `resources.bugtracker`
- `resources.x_screenshot`
- `ksp_version`
- `release_date`

###### `#/ckan/curse/:cid`

Expand Down Expand Up @@ -778,6 +780,8 @@ When used, the following fields will be auto-filled if not already present:
- `download_hash`
- `download_content_type`
- `resources.repository`
- `resources.bugtracker`
- `release_date`

Optionally, one of `asset_match` with `:filter_regexp` *or* `version_from_asset` with `:version_regexp` *may* be provided:

Expand Down Expand Up @@ -811,6 +815,7 @@ The following fields will be auto-filled if not already present:
- `download_hash`
- `download_content_type`
- `resources.ci`
- `release_date`

An `x_netkan_jenkins` field may be provided to customize how the metadata is fetched from the Jenkins server. It is
an `object` with the following fields:
Expand Down Expand Up @@ -892,6 +897,10 @@ The following conditions apply:
- A metanekan may not reference another metanetkan, otherwise an error is produced.
- Any fields specified in the metanetkan will override any fields in the target netkan file.

When used, the following fields will be auto-filled if not already present:

- `resources.metanetkan`

An example `.netkan` including all required fields for a valid metanetkan:

```yaml
Expand Down