I've updated this PR now. Added a “cannot be null” text to its value, although I personally feel like it's a bit redundant because of the already mentioned allowed values. Nevertheless, it doesn't hurt to have it there.
Default status to completed
Right, that makes sense, except I feel like that should be covered by its “Value”:
One of completed, inProgress, halted, draft
I can change this PR to remove the erroneous description and possibly set “Required” to false if you want, or we can close this and make another. Which do you prefer? :slightly_smiling_face:
So it would seem, but what about its description then?
Defaults to
completed
if targeting 100% rollout,halted
for 0%, andinProgress
for anything in between.
Also, if it's marked as required, I would guess it was required to pass it in scripts, which, if it has a default, doesn't make sense. Perhaps I'm just misunderstanding something here, I just find the current combination of description, default and required being true to be confusing.
Add work computer profile
Configure Git to always sign commits and tags
Add new dots config.yml file
Configure Git to always sign commits
Configure Git to always sign commits
Configure Git to always sign commits
Configure Git to always sign commits
Configure Git to always sign commits
Configure Git to always sign commits
The “status” input is required to specify and does not have a default, so remove “defaults to completed
” from its description.
I don't know why the Norwegian days are formatted like that by default.
Most likely because it's correct when rendering the day together with the month, e.g. “12. september” (vs. the American “September 15” style).