AGWA / AGWA/git-crypt

Committing file in .gitattributes but with no added keys commits plaintext

未关闭
#123 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
C++
星标
9.9k
派生
544
PR 合并指标
30 天内没有已合并 PR

描述

With version 0.5.0, I clone a repo with a `.gitattributes` file that matches a missing file. The repo has no added PGP keys. Even if I run `git-crypt init`, if I add the previous missing file and commit it, it's committed in plain text (which can be checked by cloning this local repo again somewhere else and running `git-crypt status -e` there).

I know that committing such file is pointless without added keys, but to avoid incidents, git-crypt could check before committing a supposedly encrypted file that it won't be encrypted, and produce an error.

Thank you!

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。