mister-bump | Utility to increment git version numbers
kandi X-RAY | mister-bump Summary
kandi X-RAY | mister-bump Summary
mister-bump is a Python library. mister-bump has no bugs, it has no vulnerabilities, it has build file available and it has low support. You can install using 'pip install mister-bump' or download it from GitHub, PyPI.
mister_bump is a Python-based tool for handling version numbering in Git projects. It can be used from within Python via import, or via the command line. The idea is to automate the creation of version numbers within Git projects. This can be done by using the tool in a projects' CI/CD build pipeline.
mister_bump is a Python-based tool for handling version numbering in Git projects. It can be used from within Python via import, or via the command line. The idea is to automate the creation of version numbers within Git projects. This can be done by using the tool in a projects' CI/CD build pipeline.
Support
Quality
Security
License
Reuse
Support
mister-bump has a low active ecosystem.
It has 2 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 12 months.
mister-bump has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of mister-bump is 1.3.0rc1
Quality
mister-bump has no bugs reported.
Security
mister-bump has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
mister-bump does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
mister-bump releases are available to install and integrate.
Deployable package is available in PyPI.
Build file is available. You can build the component from source.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi has reviewed mister-bump and discovered the below as its top functions. This is intended to give you an instant insight into mister-bump implemented functionality, and help decide if they suit your requirements.
- Bump the version number .
- Parse a version string .
- Get the current git version .
- Format a version .
- Return the type of the given version .
- Run git describe command .
- Increment the version .
- Check if a branch name is a bugfix .
- Fetch from origin .
- Parse command line arguments .
Get all kandi verified functions for this library.
mister-bump Key Features
No Key Features are available at this moment for mister-bump.
mister-bump Examples and Code Snippets
No Code Snippets are available at this moment for mister-bump.
Community Discussions
No Community Discussions are available at this moment for mister-bump.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install mister-bump
Installation can be done via pip.
Make sure the mister_bump package is installed where your CI pipeline will run. This could be a case of installing on a server, adding the package to a Docker image, or simply pip installing it within the CI pipeline. Normally you add versioning because you want to deploy something as part of your CI pipeline. Set your pipeline up to perform deployment from the master branch (for release candidates), and release-* branches (for releases). You can optionally add deployment for bugfix-* branches for bugfix release candidates. Do not perform deployment on release-*-final branches (more on that later), so add an exclusion for that too.
Make sure the mister_bump package is installed where your CI pipeline will run. This could be a case of installing on a server, adding the package to a Docker image, or simply pip installing it within the CI pipeline. Normally you add versioning because you want to deploy something as part of your CI pipeline. Set your pipeline up to perform deployment from the master branch (for release candidates), and release-* branches (for releases). You can optionally add deployment for bugfix-* branches for bugfix release candidates. Do not perform deployment on release-*-final branches (more on that later), so add an exclusion for that too.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page