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

CHEF-2541 Restore rubygem reference #3

Merged
merged 1 commit into from
May 8, 2023

Conversation

vkarve-chef
Copy link

Description

Restoring rubygems reference from chefspec-chef to chefspec

Related Issue

As we have push access to this gem in rubygems, we can allow users to continue with the same gem name.

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.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

Signed-off-by: Vikram Karve <vikram.karve@progress.com>
@vkarve-chef vkarve-chef merged commit 1e7b38a into main May 8, 2023
3 checks passed
@vkarve-chef vkarve-chef changed the title Restore rubygem reference CHEF-2541 Restore rubygem reference May 29, 2023
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.

None yet

2 participants