Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add option to sign the initial commit on production branch when creating a new repository with git flow init #59

Closed
ChrisJStone opened this issue Jul 4, 2023 · 0 comments · Fixed by #62
Closed

Add option to sign the initial commit on production branch when creating a new repository with git flow init #59

ChrisJStone opened this issue Jul 4, 2023 · 0 comments · Fixed by #62
Assignees
@ChrisJStone
Labels
enhancement github Priority: Medium
Milestone
2.2.0

Comments

@ChrisJStone
Copy link
Member

When setting up branch protection rules for a repository on GitHub a project maintainer can require that all commits made to the protected branch be signed and verified. This will necessitate the need for the initial commit to be signed as well. This is the first step in the implementation of RFC #46
@ChrisJStone ChrisJStone added this to the 2.2.0 milestone Jul 4, 2023
@ChrisJStone ChrisJStone self-assigned this Jul 4, 2023
@ChrisJStone ChrisJStone moved this to 🏗 In progress in gitflow-cjs Jul 4, 2023
ChrisJStone added a commit to ChrisJStone/gitflow-cjs that referenced this issue Jul 4, 2023
@ChrisJStone
feat(init): add sign flag to create signed commit
18b05aa 
The -g, --sign flag will create a gpg-signed commit when creating the
production branch in a new git repository. This will allow for the
option to use the Require Signed Commits branch protection rule on
GitHub.

closes CJ-Systems#59
@ChrisJStone ChrisJStone mentioned this issue Jul 4, 2023
Merged
ChrisJStone added a commit that referenced this issue Jul 4, 2023
@ChrisJStone
Merge pull request #62 from ChrisJStone/develop
48596d7 
* docs: update copyright information in source files

* docs: update repository url in source files

* feat(init): add sign flag to create signed commit

The -g, --sign flag will create a gpg-signed commit when creating the
production branch in a new git repository. This will allow for the
option to use the Require Signed Commits branch protection rule on
GitHub.

closes #59
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in gitflow-cjs Jul 4, 2023
@ChrisJStone ChrisJStone mentioned this issue Jul 6, 2023
Merged
ChrisJStone added a commit that referenced this issue Jul 6, 2023
@ChrisJStone
docs(changelog): add release notes
e337c88 
* feat(git-flow): add support for busybox(#12)

* feat(init): add support for environment credentials (#19)

Allows git flow to fall back to the same environment variables git uses
for setting the author and committer details if they are not present in
the users .gitconfig

* feat(init): add option to sign initial commit (#59)

When running git flow init the following option is now available when
creating a git repository using git flow..

1) -g, --[no]sign	Sign initial commit when creating a repository

When setting up git flow in a freshly created git repository with no
prior commits or when using git flow to create a git repository in an
existing folder the sign flag will create a signed empty commit with the
message initial commit.

* feat(feature): add feature release command (#64)

Added git flow feature release to provide a quick way to create a
release branch from a existing feature branch.

* fix(hotfix): git flow hotfix track fails due to branch name check (#68)
* feat(hotfix): add cherrypick option to hotfix finish (#73)
* feat(hotfix): add  backmerge option to release branch (#71)
* fix(hotfix): git flow hotfix finish -b back-merges to develop (#66)

When runing hotfix finish the following options have been the following
options have been added:

1) -r, --releaseBackmerge	Back-merge to release branch if exists
2) -c, --cherrypick		Cherry Pick to develop instead of merge
3) -b, --[no]nobackmerge	Don't merge master, or tag onto develop

NOTE: One one of the above three options can be used at any given time
since it doesn't make sence to combine them.

* fix(log): fix git flow log help message (#15)

git flow log help no longer implies it can only be used with feature
branches
ChrisJStone added a commit that referenced this issue Jul 6, 2023
@ChrisJStone @filipekiss
@Shea690901 @codesurf42 @adamrodger @blooper05 @simonweil
Release/2.2.0 (#74)
56cd71a 
* feat(git-flow): add support for busybox(#12)

* feat(init): add support for environment credentials (#19)

Allows git flow to fall back to the same environment variables git uses
for setting the author and committer details if they are not present in
the users .gitconfig

* feat(init): add option to sign initial commit (#59)

When running git flow init the following option is now available when
creating a git repository using git flow..

1) -g, --[no]sign	Sign initial commit when creating a repository

When setting up git flow in a freshly created git repository with no
prior commits or when using git flow to create a git repository in an
existing folder the sign flag will create a signed empty commit with the
message initial commit.

* feat(feature): add feature release command (#64)

Added git flow feature release to provide a quick way to create a
release branch from a existing feature branch.

* fix(hotfix): git flow hotfix track fails due to branch name check (#68)
* feat(hotfix): add cherrypick option to hotfix finish (#73)
* feat(hotfix): add  backmerge option to release branch (#71)
* fix(hotfix): git flow hotfix finish -b back-merges to develop (#66)

When runing hotfix finish the following options have been the following
options have been added:

1) -r, --releaseBackmerge	Back-merge to release branch if exists
2) -c, --cherrypick		Cherry Pick to develop instead of merge
3) -b, --[no]nobackmerge	Don't merge master, or tag onto develop

NOTE: One one of the above three options can be used at any given time
since it doesn't make sence to combine them.

* fix(log): fix git flow log help message (#15)

git flow log help no longer implies it can only be used with feature
branches

* chore(release): release version 2.2.0

---------

Signed-off-by: Shea690901 <[email protected]>
Co-authored-by: Filipe Kiss <[email protected]>
Co-authored-by: Shea690901 <[email protected]>
Co-authored-by: Dmitry Bogatov <git#[email protected]>
Co-authored-by: ab <[email protected]>
Co-authored-by: Adam Rodger <[email protected]>
Co-authored-by: Bankers, R.H.M. (Rob) <[email protected]>
Co-authored-by: blooper05 <[email protected]>
Co-authored-by: simonweil  <[email protected]>
ChrisJStone added a commit that referenced this issue Jul 6, 2023
@ChrisJStone
Release/2.2.0 (#75)
42ec5a7 
* docs(changelog): add release notes

* feat(git-flow): add support for busybox(#12)

* feat(init): add support for environment credentials (#19)

Allows git flow to fall back to the same environment variables git uses
for setting the author and committer details if they are not present in
the users .gitconfig

* feat(init): add option to sign initial commit (#59)

When running git flow init the following option is now available when
creating a git repository using git flow..

1) -g, --[no]sign	Sign initial commit when creating a repository

When setting up git flow in a freshly created git repository with no
prior commits or when using git flow to create a git repository in an
existing folder the sign flag will create a signed empty commit with the
message initial commit.

* feat(feature): add feature release command (#64)

Added git flow feature release to provide a quick way to create a
release branch from a existing feature branch.

* fix(hotfix): git flow hotfix track fails due to branch name check (#68)
* feat(hotfix): add cherrypick option to hotfix finish (#73)
* feat(hotfix): add  backmerge option to release branch (#71)
* fix(hotfix): git flow hotfix finish -b back-merges to develop (#66)

When runing hotfix finish the following options have been the following
options have been added:

1) -r, --releaseBackmerge	Back-merge to release branch if exists
2) -c, --cherrypick		Cherry Pick to develop instead of merge
3) -b, --[no]nobackmerge	Don't merge master, or tag onto develop

NOTE: One one of the above three options can be used at any given time
since it doesn't make sence to combine them.

* fix(log): fix git flow log help message (#15)

git flow log help no longer implies it can only be used with feature
branches

* chore(release): release version 2.2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChrisJStone ChrisJStone

Labels
enhancement github Priority: Medium
Projects
gitflow-cjs
Status: ✅ Done
Milestone
2.2.0
1 participant
@ChrisJStone