We do not use a "plugin system" for Git addons anymore, and therefore this directory is no longer useful. Indeed that directory is way more confusing, given that it includes more than mere Git addons, going from Bitbucket server command-line tools to complete rewrites of Git in exotic programming languages. Also, without this directory, the mental load of decision-making reduces a lot. When anyone is interested in including a new git-related tool, just put it into pkgs/applications/version-management, without apologies.
41 lines
1.3 KiB
Nix
41 lines
1.3 KiB
Nix
{ lib, stdenv, fetchFromGitHub, python3 }:
|
|
|
|
stdenv.mkDerivation rec {
|
|
pname = "git-when-merged";
|
|
version = "1.2.0";
|
|
|
|
src = fetchFromGitHub {
|
|
owner = "mhagger";
|
|
repo = pname;
|
|
rev = "v${version}";
|
|
sha256 = "0sw98gmsnd4iki9fx455jga9m80bxvvfgys8i1r2fc7d5whc2qa6";
|
|
};
|
|
|
|
buildInputs = [ python3 ];
|
|
|
|
installPhase = ''
|
|
install -D --target-directory $out/bin/ bin/git-when-merged
|
|
'';
|
|
|
|
meta = with lib; {
|
|
description =
|
|
"Helps you figure out when and why a commit was merged into a branch";
|
|
longDescription = ''
|
|
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 = licenses.gpl2Only;
|
|
platforms = python3.meta.platforms;
|
|
maintainers = with maintainers; [ DamienCassou ];
|
|
};
|
|
}
|