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

Use online config-schema.json instead of local #134

Open
bullmoose20 opened this issue Jul 13, 2024 · 4 comments
Open

Use online config-schema.json instead of local #134

bullmoose20 opened this issue Jul 13, 2024 · 4 comments
Milestone

Comments

@bullmoose20
Copy link
Collaborator

No description provided.

@bullmoose20
Copy link
Collaborator Author

The question is which url we should use in QuickStart instead of the local.

Master, Develop, Nightly?

@bullmoose20
Copy link
Collaborator Author

Or maybe there is a git action that always gets updated based on the Kometa master branch config-schema.json?

Clearly I am getting all mixed up and wondering how we handle QuickStart with the different branches of Kometa.

@chazlarson
Copy link
Contributor

I suppose there could be three branches of quickstart

@bullmoose20 bullmoose20 added this to the MVP milestone Jul 18, 2024
@bullmoose20
Copy link
Collaborator Author

I guess the issue is that if we want to follow what kometa does, then I am not sure how to implement this so that we keep the yaml validation in sync with any/all of the schema-config.json files in the three different branches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants