puppetlabs/vmpooler-provider-vsphere
2
0
Fork 0
mirror of https://github.com/puppetlabs/vmpooler-provider-vsphere.git synced 2026-01-25 19:08:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Revert "Migrate issue management to Jira"

Browse source 
This reverts commit 2f0e817b7c.
This commit is contained in:
Jake Spain 2023-04-20 08:51:12 -04:00
parent 801aaa743c
commit 9e31ed815f
No known key found for this signature in database
GPG key ID: BC1C4DA0A085E113
1 changed files with 0 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -4,7 +4,6 @@
- [Usage](#usage)
- [Custom VM Config Attribute](#custom-vm-config-attribute)
- [Update the Gemfile Lock](#update-the-gemfile-lock)
- [Submitting Issues](#submitting-issues)
- [Releasing](#releasing)
- [License](#license)
@ -31,10 +30,6 @@ To update the `Gemfile.lock` run `./update-gemfile-lock`.
Verify, and update if needed, that the docker tag in the script and GitHub action workflows matches what is used in the [vmpooler-deployment Dockerfile](https://github.com/puppetlabs/vmpooler-deployment/blob/main/docker/Dockerfile).
## Submitting Issues
Please file any issues or requests in Jira at <https://puppet.atlassian.net/jira/software/c/projects/POOLER/issues> where project development is tracked across all VMPooler related components.
## Releasing
Follow these steps to publish a new GitHub release, and build and push the gem to <https://rubygems.org>.