Skip to content

Add Hilmar to Git Crypt#99

Merged
gaurav merged 2 commits intomasterfrom
add-hilmar-to-git-crypt
Nov 12, 2025
Merged

Add Hilmar to Git Crypt#99
gaurav merged 2 commits intomasterfrom
add-hilmar-to-git-crypt

Conversation

@gaurav
Copy link
Copy Markdown
Member

@gaurav gaurav commented Nov 12, 2025

This PR adds @hlapp to Git Crypt.

New collaborators:

09266575A8EC4AA3BD2C7740073F565E8824280E
    Hilmar Lapp <hilmar.lapp@duke.edu>

New collaborators:

    09266575A8EC4AA3BD2C7740073F565E8824280E
        Hilmar Lapp <hilmar.lapp@duke.edu>
@gaurav gaurav requested a review from hlapp November 12, 2025 03:22
@hlapp
Copy link
Copy Markdown
Member

hlapp commented Nov 12, 2025

Yep works. I had actually already tested with the previously encrypted phyloreferences. That is, if I successfully git crypt unlock on this branch (which has my key added but at first didn't encrypted files present anymore) and then checkout a commit where the encrypted files are still present (but which doesn't have my key added), then the files will be decrypted.

@hlapp
Copy link
Copy Markdown
Member

hlapp commented Nov 12, 2025

Also of note, if you pull an encrypted file from remote into an unlocked repo checkout, it will be decrypted there.

More generally, unlocking or locking a repo is repo-wide and history-wide, forward and backward, not specific to a commit or file(s). (And arguably that's the most useful behavior too.)

@gaurav gaurav merged commit f1f6927 into master Nov 12, 2025
6 checks passed
@gaurav gaurav deleted the add-hilmar-to-git-crypt branch November 12, 2025 20:06
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.

2 participants