-
Notifications
You must be signed in to change notification settings - Fork 1.3k
schema: Define a relaxed schema as v1 and move current schema to v2 #769
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
Conversation
dd98dce
to
dd605fc
Compare
dd605fc
to
ee02b95
Compare
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 |
This happened this afternoon. So we can merge this PR when the backend is ready. |
@shivchander Please let us know when we can merge this and start accepting |
ee02b95
to
dfc537e
Compare
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>
dfc537e
to
1045fd0
Compare
…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>
…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>
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