Downloads:
21
Downloads of v 6.1.0:
21
Last Update:
25 Jul 2024
Package Maintainer(s):
Software Author(s):
- Paul Delafosse
Tags:
cocogitto git commit cli dev- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Cocogitto (Portable)
- 1
- 2
- 3
6.1.0 | Updated: 25 Jul 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
21
Downloads of v 6.1.0:
21
Maintainer(s):
Software Author(s):
- Paul Delafosse
Cocogitto (Portable) 6.1.0
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Paul Delafosse. The inclusion of Paul Delafosse trademark(s), if any, upon this webpage is solely to identify Paul Delafosse goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Cocogitto (Portable), run the following command from the command line or from PowerShell:
To upgrade Cocogitto (Portable), run the following command from the command line or from PowerShell:
To uninstall Cocogitto (Portable), run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download cocogitto --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade cocogitto -y --source="'INTERNAL REPO URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade cocogitto -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install cocogitto
win_chocolatey:
name: cocogitto
version: '6.1.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'cocogitto' do
action :install
source 'INTERNAL REPO URL'
version '6.1.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller cocogitto
{
Name = "cocogitto"
Version = "6.1.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'cocogitto':
ensure => '6.1.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved by moderator flcdrg on 31 Jul 2024.
The Conventional Commits toolbox
- Verified commits: create conventional compliant commits with ease.
- Automatic Version bump and changelog: automatically bump versions and generate changelogs with your own custom steps
and workflows. - Release profiles: your branching model requires different steps for releases, pre-release, hotfixes ? We got you
covered ! - Depends only on libgit2: cocogitto has one standalone binary, the only system dependency is libgit2.
- Conventional git log: search your commit history matching Conventional Commits items such as scope and commit type.
- GitHub integration: enforce the conventional commits specification with our GitHub action and bot.
- Monorepo support: Automatic versioning for mono-repositories is supported out of the box.
Foreword
What is it ?
Cocogitto is a CLI and GitOps toolbox for the Conventional Commits
and Semver specifications.
Why ?
There are plenty of tools listed on
the conventional commits website
to help you generate changelog, git hooks, commit template etc. Some of them are specifically designed for the
Conventional Commits specification, and some of them are general purpose.
Cocogitto was designed to help you respect the
conventional and semver standard and is not intended to be used in any other context.
It strives to be a set of simple, modern and fast command line interfaces.
Goals
- Make using the conventional commits spec easy and fun.
- Enable people to focus on their work instead of correcting small mistakes and typos.
- Enforce correctness regarding Semver and Conventional Commits.
- Automate things when possible (ex: bumping versions).
Non goals
- Cocogitto is not a
git
replacement. It uses some of libgit2 but only to provide features related to the
Conventional Commits specification. Anything else shall be done withgit
. - Supporting other commit conventions or git workflows.
Quick start
This readme is a quick tour of what you can do with Cocogitto, for an in-depth guide please refer
to the documentation.
Log in or click on link to see number of positives.
- cocogitto.6.1.0.nupkg (2f4a520c6421) - ## / 69
- cocogitto-6.1.0-x86_64-pc-windows-msvc.tar.gz (a3887910a31e) - ## / 65
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.
Ground Rules:
- This discussion is only about Cocogitto (Portable) and the Cocogitto (Portable) 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 Cocogitto (Portable), 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.