Skip to content

Conversation

@DannyBen
Copy link
Member

@DannyBen DannyBen commented Sep 30, 2021

wolfgang42 and others added 3 commits September 29, 2021 22:46
The bashly.yml that the spec uses does not define a "cli-get" command,
so if the generator *were* overwriting this file the spec would not
catch it. Change the spec to use a command name that the example yml
does have, so that it would be overwritten if this happens.
@DannyBen
Copy link
Member Author

I am ready to merge.

Do you wish to try it before I merge and release?

@DannyBen DannyBen changed the title Update bashly generate --init Fix and merge #109, #110 and #111 Sep 30, 2021
@wolfgang42
Copy link
Collaborator

Yes, I'm about to go to bed but I will take a closer look tomorrow after work. One quick comment:

completely quiet (even created files).

The notice about newly created files was useful, even when I wanted otherwise silent output. I'd also be fine without it but that was my reasoning for excluding it in my PR.

@wolfgang42
Copy link
Collaborator

Just tried this, LGTM (aside from my note about quieting the create messages, which as I say I don't feel too strongly about).

@DannyBen
Copy link
Member Author

DannyBen commented Oct 1, 2021

Ok, I will merge then.

About the create messages, I don't see a way around it. Quiet should be quiet. If someone is using it, they have a reason to avoid polluting the stdout, so if we pollute it even with a single character, it will be annoying.

@DannyBen DannyBen merged commit 783fc32 into master Oct 1, 2021
@DannyBen DannyBen deleted the pr/109 branch October 1, 2021 07:15
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

Successfully merging this pull request may close these issues.

say is not defined in Runfile

3 participants