Skip to content

Conversation

bjhargrave
Copy link
Contributor

We introduce a relaxed schema as v1 which will accept all existing taxonomy files in the main branch of the taxonomy repo. The current v1 schema is renamed to v2 and will be used for future contributions to the taxonomy repo.

The check_yaml script is updated to allow a schema version to be specified. When the schema-version option is not specified, the script will use the latest schema version from the schema base. If the schema-version is specified as a non-positive integer, then the script will use the version key from the YAML document for the schema version to use.

The script is also changed to only check for attribution.txt when the schema version is higher than 1.

See instructlab/instructlab#989

Depends on instructlab/schema#11

@github-actions github-actions bot added the ci label Apr 25, 2024
@github-actions github-actions bot added documentation Improvements or additions to documentation triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels Apr 26, 2024
@instructlab instructlab deleted a comment from instruct-lab-bot bot Apr 26, 2024
@bjhargrave bjhargrave removed triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels Apr 26, 2024
@github-actions github-actions bot added triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels Apr 29, 2024
@bjhargrave
Copy link
Contributor Author

Before merging this PR, we should probably wait until the cli containing instructlab/instructlab#1009 is published. If we merge before then, then we will require version: 2 while the cli will not accept version: 2.

@instructlab instructlab deleted a comment from instruct-lab-bot bot Apr 29, 2024
@bjhargrave bjhargrave removed triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels Apr 29, 2024
@bjhargrave
Copy link
Contributor Author

Before merging this PR, we should probably wait until the cli containing instructlab/instructlab#1009 is published.

This happened this afternoon. ilab has released v0.14.0 (aka stable) which includes the version: 2 schema support.

So we can merge this PR when the backend is ready.

@bjhargrave
Copy link
Contributor Author

So we can merge this PR when the backend is ready.

@shivchander Please let us know when we can merge this and start accepting version: 2 in the qna.yaml. Thanks.

@github-actions github-actions bot added triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels May 20, 2024
@instructlab instructlab deleted a comment from instruct-lab-bot bot May 20, 2024
@bjhargrave bjhargrave removed triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels May 20, 2024
We introduce a relaxed schema as v1 which will accept all existing
taxonomy files in the main branch of the taxonomy repo. The current
v1 schema is renamed to v2 and will be used for future contributions
to the taxonomy repo.

The check_yaml script is updated to allow a schema version to
be specified. When the schema-version option is not specified, the
script will use the latest schema version from the schema base.
If the schema-version is specified as a non-positive integer, then the
script will use the version key from the YAML document for the schema
version to use.

The script is also changed to only check for attribution.txt when the
schema version is higher than 1.

See instructlab/instructlab#989

Depends on instructlab/schema#11

Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
@github-actions github-actions bot added the triage-needed (Auto labeled) skill is ready to be triaged label May 21, 2024
@github-actions github-actions bot added the knowledge (Auto labeled) label May 21, 2024
@instructlab instructlab deleted a comment from instruct-lab-bot bot May 21, 2024
@bjhargrave bjhargrave removed triage-needed (Auto labeled) skill is ready to be triaged knowledge (Auto labeled) labels May 21, 2024
@jjasghar jjasghar merged commit 17e4718 into instructlab:main May 23, 2024
@bjhargrave bjhargrave deleted the relaxed-schema branch May 28, 2024 20:41
jjasghar pushed a commit to luke-inglis/taxonomy that referenced this pull request Jun 7, 2024
…nstructlab#769)

We introduce a relaxed schema as v1 which will accept all existing
taxonomy files in the main branch of the taxonomy repo. The current v1
schema is renamed to v2 and will be used for future contributions to the
taxonomy repo.

The check_yaml script is updated to allow a schema version to be
specified. When the schema-version option is not specified, the script
will use the latest schema version from the schema base. If the
schema-version is specified as a non-positive integer, then the script
will use the version key from the YAML document for the schema version
to use.

The script is also changed to only check for attribution.txt when the
schema version is higher than 1.

See instructlab/instructlab#989

Depends on instructlab/schema#11

Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
jjasghar pushed a commit to acidonper/taxonomy that referenced this pull request Jun 10, 2024
…nstructlab#769)

We introduce a relaxed schema as v1 which will accept all existing
taxonomy files in the main branch of the taxonomy repo. The current v1
schema is renamed to v2 and will be used for future contributions to the
taxonomy repo.

The check_yaml script is updated to allow a schema version to be
specified. When the schema-version option is not specified, the script
will use the latest schema version from the schema base. If the
schema-version is specified as a non-positive integer, then the script
will use the version key from the YAML document for the schema version
to use.

The script is also changed to only check for attribution.txt when the
schema version is higher than 1.

See instructlab/instructlab#989

Depends on instructlab/schema#11

Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants