-
Notifications
You must be signed in to change notification settings - Fork 177
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 config for yadm to create read-only template output #454
base: develop
Are you sure you want to change the base?
Conversation
A slight bump on this PR: are there any more blockers for merging this PR? |
I adjusted this PR to target the develop branch. Can tests and updates to the manpage be added? |
Hi @TheLocehiliosan ! Man and tests had been added! |
@soraxas - I updated the pull request to target the develop branch, but there are conflicts. Can you rebase your branch to be on top of the develop branch? |
Signed-off-by: Tin Lai <[email protected]>
Signed-off-by: Tin Lai <[email protected]>
Signed-off-by: Tin Lai <[email protected]>
@TheLocehiliosan A slight bump on this PR again |
What does this PR do?
Allow user to tell
yadm
to create read-only template outputWhat issues does this PR fix or reference?
I always forget that the file I'm editing is an output from
yadm
template :( and loss my editing. (despite already adding a header notice on the top of the file)Config via:
$ yadm config yadm.template-read-only true
Previous Behavior
yadm
copies permsNew Behavior
yadm
copies perms, and optionally, remove write permsHave [tests][1] been written for this change?
No
Have these commits been [signed with GnuPG][2]?
Yes
P.S.
This is a global control.
An alternative solution, that allows per-file controls, is to allow template file to have some extra parameters, e.g.,
my_config.toml##<condition>,template.esh,template.ro=true
but the original semantic of those values were conditions, so I'm not sure if that'd be a good approach