Ansible
PS DSC
Downloads:
19
Downloads of v 1.0.0:
19
Last Update:
23 Jul 2024
Published Date:
23 Jul 2024
Package Maintainer(s):
Software Author(s):
- Guhan
Tags:
good-commit git commit conventional-commit- Software Specific:
- Software Site
- Software Source
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
good-commit
(Maintainer responded, waiting for review/Maintainer update)
- 1
- 2
- 3
1.0.0 | Updated: 23 Jul 2024
- Software Specific:
- Software Site
- Software Source
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
19
Downloads of v 1.0.0:
19
Published:
23 Jul 2024
Maintainer(s):
Software Author(s):
- Guhan
good-commit 1.0.0
(Maintainer responded, waiting for review/Maintainer update)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
IMPORTANT
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
WARNING
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
Description
A CLI tool to create git commits following conventional commit standards
Files
tools\chocolateybeforemodify.ps1
tools\chocolateyinstall.ps1
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = 'good-commit*'
fileType = 'EXE_MSI_OR_MSU'
silentArgs = "/qn /norestart"
validExitCodes= @(0, 3010, 1605, 1614, 1641)
}
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)"
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
tools\LICENSE.txt
From: https://opensource.org/licenses/MIT
LICENSE
MIT License
Copyright (c) [year] [fullname]
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The checksum hash for the cli's binary is at "releases\good-commit-cli.json".
It will ALWAYS BE the hash of the latest version's binary generated by the software's author,
updated in the Github repository whenever a new version is released.
Virus Scan Results
Log in or click on link to see number of positives.
- good-commit.1.0.0.nupkg (6732c40c59d9) - ## / 67
- good-commit-cli.exe (9ee710a1ea78) - ## / 73
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Dependencies
This package has no dependencies.
Discussion for the good-commit Package
Ground Rules:
- This discussion is only about good-commit and the good-commit package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or good-commit, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
gukkey (maintainer) on 23 Jul 2024 18:16:23 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 18:37:42 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 18:39:07 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 18:42:52 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 18:55:35 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 18:58:15 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 19:04:39 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 19:06:09 +00:00:
User 'gukkey' (maintainer) submitted package.
gukkey (maintainer) on 23 Jul 2024 19:08:39 +00:00:
User 'gukkey' (maintainer) submitted package.
chocolatey-ops (reviewer) on 23 Jul 2024 19:43:18 +00:00:
good-commit has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
gukkey (maintainer) on 23 Jul 2024 20:59:16 +00:00:
User 'gukkey' (maintainer) submitted package.
chocolatey-ops (reviewer) on 23 Jul 2024 21:33:44 +00:00:
good-commit has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 23 Jul 2024 21:38:11 +00:00:
good-commit has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/85fd24af086ec9c7f39fb531e0176e72 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 23 Jul 2024 21:51:19 +00:00:
good-commit has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
gukkey (maintainer) on 25 Jul 2024 18:46:23 +00:00:
I think that might be a false negative.