Merge pull request #107012 from DamienCassou/DamienCassou/git-when-merged
gitAndTools.git-when-merged: init at 1.2.0
This commit is contained in:
commit
b3f079e40c
@ -172,6 +172,8 @@ let
|
||||
inherit (darwin.apple_sdk.frameworks) Security;
|
||||
};
|
||||
|
||||
git-when-merged = callPackage ./git-when-merged { };
|
||||
|
||||
git-workspace = callPackage ./git-workspace {
|
||||
inherit (darwin.apple_sdk.frameworks) Security;
|
||||
};
|
||||
|
@ -0,0 +1,40 @@
|
||||
{ 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 stdenv.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 ];
|
||||
};
|
||||
}
|
Loading…
Reference in New Issue
Block a user