-
Notifications
You must be signed in to change notification settings - Fork 0
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
add --no-init option to gut template generate #131
Labels
critical-path
This task is required to be completed by a given delivery date.
Comments
snomos
added
the
critical-path
This task is required to be completed by a given delivery date.
label
May 21, 2020
This is also covered in issue #44 but I keep this open, as it contains additional info and use cases. |
An option |
snomos
changed the title
gut create repo needs a template option
add --no-init option to gut template generate
May 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a new repo, there should be an option to specify a template repo to pre-populate the new repo with content. When using such a template, also the
.gut/
dir should be automatically configured for future delta updates, and all string replacements should be carried out.This option requires another option: the 3-letter language code. From that code, one can derive the two-letter code (if it exists), and also the English language name.
A variant of the create new repo command is to superimpose the template structure on an existing repo, typically when outside projects would like to use our infra to produce spellers and other tools. The outside repo is transfered to our org, and then needs to be given the same setup as the other languages. Applying or superimposing the template repo content fills that need (with some reorganisation of the exising content afterwards).
I have labelled this with critical-path, as there is a need to have this functionality in place very soon, there will certainly be a need for adding new languages (both completely new and existing outside projects) in the near future, when collaboration with Canada starts for real.
The text was updated successfully, but these errors were encountered: