bump_version | Go tool for bumping version numbers

by Shyp Go Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | bump_version Summary

bump_version is a Go library. bump_version has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This is a tool for bumping version numbers in Go files.

Support

Quality

Security

License

Reuse

Support

bump_version has a low active ecosystem.

It has 13 star(s) with 3 fork(s). There are 14 watchers for this library.

It had no major release in the last 6 months.

bump_version has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of bump_version is current.

Quality

bump_version has no bugs reported.

Security

bump_version has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

bump_version is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

bump_version releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed bump_version and discovered the below as its top functions. This is intended to give you an instant insight into bump_version implemented functionality, and help decide if they suit your requirements.

Parse parses a version string into a Version object .
main is the entry point for testing
changeVersion changes a version of the given version
findBasicLit searches for a BasicLit .
changeInFile runs the given function on the given file with the given function .
BumpInFile dumps a version of a version to a version .
String returns a string representation of the version
writeFile prints a file to a file
runCommand runs the given command and returns the output .
SetInFile changes the version of a version .

Get all kandi verified functions for this library.

bump_version Key Features

No Key Features are available at this moment for bump_version.

bump_version Examples and Code Snippets

No Code Snippets are available at this moment for bump_version.

Community Discussions

Trending Discussions on bump_version

Git push action is not working when pushing from git action container

How can I bump the package.json version when I commit based on the commit message?

QUESTION

Git push action is not working when pushing from git action container

Asked 2019-Dec-02 at 20:51

I have an action on master branch which on push/merge builds a package, uploads it to PyPI then checks out to develop branch, bumps version in develop branch and pushes to the origin of develop branch. Develop branch has an action that listens to push/merge and does a snapshot release. When I push to develop the develop action works perfectly and does a snapshot release, but when master branch pushes, push is successful but the action does not get triggered. What am I missing? Both actions are added below.

...

ANSWER

Answered 2019-Dec-02 at 20:51

Provided secrets.GITHUB_TOKEN is intentionally not allowed to trigger workflows. As seen in documention:

(...) if an action pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.

If you need your automagic push to be "visible" by workflows, you need to create Personal Access Token, add it to repo secrets, and use that instead of GITHUB_TOKEN.

Note that GitHub assumes that you know what you're doing, if you use non-stock token - which means preventing possible infinite loop is on you. While it's not a case in your scenario for now (develop branch does not push anything), it's worth to remember in case one of workflows will change some day.

Source https://stackoverflow.com/questions/59145302

QUESTION

How can I bump the package.json version when I commit based on the commit message?

Asked 2019-Mar-30 at 03:21

I am trying to bump the version of my package.json file when I commit, but only if the commit message is prefixed correctly: MJ prefix triggers a patch bump, ^ prefix triggers a minor bump. I wrote a gulp task to do this and it works, the only problem is that I can't get the message of the current commit, execute the task, then add package.json to the commit and continue.

I tried running my task on these two git hooks:

pre-commit

Problem:

I only have access the previous commit message in this hook, not the one we're doing right now.

What works

I can bump the version, but only based on the previous commit message
I can stage package.json
package.json can then be added to the commit along with the rest

prepare-commit-msg

Problem:

staging package.json does not add it to the commit

What works

I can bump the version based on the current commit message
I can stage package.json

This is my gulp task that I've tried with the two hooks. I removed some noise to try to keep it minimal.

...

ANSWER

Answered 2019-Mar-30 at 03:21

You can use the commit-msg hook to read the commit message, take actions based on that, stage files and commit

.git/hooks/commit-msg

Source https://stackoverflow.com/questions/55427220

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install bump_version

For the moment, you'll need a working Go installation. That will install the bump_version binary to your $GOPATH.

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: