git-when-merged

git-when-merged 1.2.1 · pkgs/by-name/gi/git-when-merged/package.nix

Health

Risk

risk 1 low

+1 no versionCheckHook

Version

1.2.1 no newer release known to repology

Channels

master 1.2.1 · nixos-unstable 1.2.1 · nixos-26.05 1.2.1 no channel is behind master

Hydra

succeeded 2w ago

Advisories

none open

Packaging

no versionCheckHook

Packagewhat each field means

Description

Helps you figure out when and why a commit was merged into a branch

Long description

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?"

Homepage

https://github.com/mhagger/git-when-merged

License

GPL-2.0-only

Platforms

31 platforms: Linux, Darwin

Main program

git-when-merged

Source provenance

not set: built from source

Outputs

out