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

Updated the error message and start message branding #17

Merged
merged 2 commits into from
Nov 27, 2024

Conversation

ashiqueps
Copy link

Description

Updated the error message to include the kitchen license command information to let the user know how to generate the license.
Updated the starting and ending messages with the rebranded name.

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

@ashiqueps ashiqueps requested review from a team as code owners November 27, 2024 11:08
Signed-off-by: Ashique Saidalavi <[email protected]>
@Stromweld
Copy link

I'm wondering if we should contribute back to the community test-kitchen repo a product name substitution to make future updates and pulling in of parent repo updates easier. This would be similar to the work done in chef/chef repo to support cinc builds but now in reverse to support our enterprise fork.

@ashiqueps ashiqueps merged commit 13b3fbf into main Nov 27, 2024
8 of 11 checks passed
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.

5 participants