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.

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

Many gpg keys v2 #297

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Many gpg keys v2 #297

wants to merge 2 commits into from

Conversation

ibotty
Copy link

@ibotty ibotty commented Oct 25, 2024

supersedes #256, closes #103.

@ibotty ibotty requested a review from oknozor as a code owner October 25, 2024 08:43
Copy link

cocogitto-bot bot commented Oct 25, 2024

❌ Found 105 compliant commit and 6 non-compliant commits in cfcfdd9...a571140.

Commit cfcfdd9 by @mrkajetanp is not conform to the conventional commit specification :

  • message: mrkajetanp's dotfiles in example repositories
  • cause:
    Missing commit type separator `:`
    
    Caused by:
         --> 1:11
          |
        1 | mrkajetanp's dotfiles in example repositories
          |           ^---
          |
          = expected scope or type_separator
    

Commit c803bfb by @oknozor is not conform to the conventional commit specification :

  • message: refacor: split paths and settings into dedicated modules
  • cause:
    Errored commit: not committed <oknozor>
    	Commit message:'refacor: split paths and settings into dedicated modules'
    	Error:Commit type `refacor` not allowed
    

Commit 8449e66 by @ShoyuVanilla is not conform to the conventional commit specification :

  • message: Minor typo
  • cause:
    Missing commit type separator `:`
    
    Caused by:
         --> 1:6
          |
        1 | Minor typo
          |      ^---
          |
          = expected scope or type_separator
    

Commit 6aad90a by @ibotty is not conform to the conventional commit specification :

  • message: `allow encrypting/decrypting to/from multiple keys

This uses the key gpg_user_ids, but keeps gpg_user_id as alias for
backwards compatibility.`

  • cause:
    Missing commit type separator `:`
    
    Caused by:
         --> 1:6
          |
        1 | allow encrypting/decrypting to/from multiple keys
          |      ^---
          |
          = expected scope or type_separator
    

Commit 4443ac5 by @ibotty is not conform to the conventional commit specification :

  • message: `remove trailing whitespace in gpg docs

This was showing up in the syntax highlighting.`

  • cause:
    Missing commit type separator `:`
    
    Caused by:
         --> 1:7
          |
        1 | remove trailing whitespace in gpg docs
          |       ^---
          |
          = expected scope or type_separator
    

Commit a571140 by @ibotty is not conform to the conventional commit specification :

  • message: update readme for multiple gpg keys
  • cause:
    Missing commit type separator `:`
    
    Caused by:
         --> 1:7
          |
        1 | update readme for multiple gpg keys
          |       ^---
          |
          = expected scope or type_separator
    

@ibotty
Copy link
Author

ibotty commented Oct 25, 2024

Oh, something went wrong. Wait a sec.

Now it's alright.

This uses the key `gpg_user_ids`, but keeps `gpg_user_id` as alias for
backwards compatibility.

Fixes oknozor#103.
@oknozor
Copy link
Owner

oknozor commented Oct 27, 2024

I think we need a few tests with multiple GPG ids.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEATURE] List of gpg keys to encryt secrets for
2 participants