Open eduard93 opened 1 year ago
@eduard93 you could just get a new instance of SourceControl.Git.Settings, set properties of it, and then call %Save().
That said, we should document how to do that and make it part of the official API (from a semantic versioning perspective).
Would that be enough? I looked at the method generator in SourceControl.Git.Settings:Configure
and it looked like it just prompted for values, but I want to be sure.
It does that and some other interactive things based on what's changed.
Ultimately there are enough settings that the API should be an object anyway, rather than a method with a growing # of parameters.
Leaving this issue open open to flag the class as part of the API and document how to use it.
Would it be possible to add non-interactive alternative to
SourceControl.Git.API:Configure
, especiallySourceControl.Git.Settings:Configure
. I want to provide all values in a script.