git-when-merged | particular commit was merged into a git branch

by mhagger Python Version: 6.6.6 License: GPL-2.0

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

kandi X-RAY | git-when-merged Summary

git-when-merged is a Python library. git-when-merged has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. However git-when-merged build file is not available. You can install using 'pip install git-when-merged' or download it from GitHub, PyPI.

git when-merged helps you figure out when and why a commit was merged into a branch. If you use standard Git workflows, then you create a feature branch for each feature that you are working on. When the feature is complete, you merge it into your master branch. You might even have sub-feature branches that are merged into a feature branch before the latter is merged. In such a workflow, the first-parent history of master consists mainly of merges of feature branches into the mainline. git when-merged can be used to ask, "When (and why) was commit C merged into the current branch?" The simplest way to use it is.

Support

Quality

Security

License

Reuse

Support

git-when-merged has a low active ecosystem.

It has 344 star(s) with 18 fork(s). There are 15 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 5 have been closed. On average issues are closed in 81 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of git-when-merged is 6.6.6

Quality

git-when-merged has 0 bugs and 0 code smells.

Security

git-when-merged has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

git-when-merged code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

git-when-merged is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

git-when-merged releases are available to install and integrate.

Deployable package is available in PyPI.

git-when-merged has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

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

Yield the parents of the given commit
Generate the first commit path
Decode the output
Verify a git revision
Run git output
Name of a commit
Execute git - describe command
Get the full name of the given branch
Iterate over all refnames in the git repository
Run git rev - list
Return a list of merged branch patterns
Return a list of the names of the given arguments
Return true iff the refname matches any of refnames

Get all kandi verified functions for this library.

git-when-merged Key Features

No Key Features are available at this moment for git-when-merged.

git-when-merged Examples and Code Snippets

No Code Snippets are available at this moment for git-when-merged.

Community Discussions

No Community Discussions are available at this moment for git-when-merged.Refer to stack overflow page for discussions.

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

Vulnerabilities

No vulnerabilities reported

Install git-when-merged

Clone the repo somewhere on your system.
Ensure that <somewhere>/bin/git-when-merged is executable.
Put the contents of <somewhere>/bin on your $PATH.

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: