Skip to content
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

Overhaul Chocolatey Cake aliases #4050

Closed
gep13 opened this issue Nov 7, 2022 · 1 comment · Fixed by #4051
Closed

Overhaul Chocolatey Cake aliases #4050

gep13 opened this issue Nov 7, 2022 · 1 comment · Fixed by #4051
Assignees
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Nov 7, 2022

Since the original release of the Chocolatey Cake aliases, there have been a number of new options added for the different commands.

In addition, best practices have been defined for how to call Chocolatey commands, in terms of using full option name, as well as preferring usage of = in the option vlaue.

We should overhaul the current Chocolatey Cake aliases taking all of the above things into consideration, as well as making sure that all common options are added to each command, with tests included for all of them.

@gep13 gep13 self-assigned this Nov 7, 2022
gep13 added a commit to gep13/cake that referenced this issue Nov 7, 2022
- Make use of full option name
- Make sure to always use = in option value
- Add common options to all commands
- Add new options that have been added since aliases first created
gep13 added a commit to gep13/cake that referenced this issue Nov 7, 2022
- Make use of full option name
- Make sure to always use = in option value
- Add common options to all commands
- Add new options that have been added since aliases first created
@devlead devlead added this to the v3.0.0 milestone Nov 7, 2022
@cake-build-bot
Copy link

🎉 This issue has been resolved in version v3.0.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants