bfg-repo-cleaner
git-crypt
bfg-repo-cleaner | git-crypt | |
---|---|---|
53 | 50 | |
10,741 | 8,037 | |
- | - | |
0.0 | 0.0 | |
29 days ago | 5 days ago | |
Scala | C++ | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bfg-repo-cleaner
-
(RE not sharing inputs) PSA: "deleting" and committing to git doesn't actually remove it
So, this is a PSA that you can't simply delete the file and commit that. You must either use a tool like BFG Repo Cleaner which can scrub files out of your commit history or you could simply delete your repository and recreate it (easier, but you lose your commit history).
-
How do you handle the different repositories in CI?
It shouldn't take a lot of time to modify. There is even a tool just for this scenario https://rtyley.github.io/bfg-repo-cleaner/
- What Is BFG?
- What is in that .git directory?
-
someThingsAreForever
You need to git out the BFG: https://rtyley.github.io/bfg-repo-cleaner/
-
How can I mirror a folder in my repo to another repo?
This method requires changes to be committed as usual in the regular project repository, and then committed again in the -docs repository. This is inelegant, but it provides clear distinction between private and public content. You cannot publish your regular repository without using git-filter-branch or some Git history rewriting software like BFG Repo-Cleaner. This would rewrite every commit in the history of the repo, removing all changes to the paths you don't wish to publish. This would change all the commit hashes and possibly other metadata – in short, it wouldn't be the same repository.
-
please help i accidentally added all my user files on my git source control how to revert that? it says it will delete all the files forever and you cannot recover them. Any solution at all please?
GFG Repo-Cleaner
- How to remove sensitive file from origin history?
-
Nintendo sends Valve DMCA notice to block Steam release of Wii emulator Dolphin
You could use a repo filtering tool (e.g. BFG Repo-Cleaner) to clean up unintended information leak from your Git repository -- which retains the history timeline, but I believe it would rehash all the commits and render everything unsigned, which is probably not the desired outcome.
- BFG Repo-Cleaner – Removes large or troublesome blobs from Git
git-crypt
-
Why Can't My Mom Email Me?
https://github.com/AGWA/git-crypt
And occasionally to encrypt files, or receive encrypted files.
These are practical things which are non-theoretical.
> Using multiple keys don't offer added security or secrecy.
Depends on how careful you are or want to be, with your private key. My house key isn't the same as my car key isn't the same as my bike key.
> This is nothing like data harvesting
Alright fair, bad example. What I was grumbling about was more the lack of any clear communication that you've been auto-opted-in to a feature on protonmail, with no user interface signal indicating so, leading to confusion for a couple months like in TFA. I definitely wasn't casting shade on the opengpg keyserver, nor protonmail. It's the "hey! I didn't check a box for this, and it's not mentioned anywhere in the protonmail docs" hidden functionality which could do with some clarification.
I'm a forgetful creature. If I intentionally put my key on a keyserver, because I'm playing around and learning about PGP, will I make the connection between it and protonmail a few months down the line if I move my email account to them? Unlikely.
It's a nice automated feature. Protonmail-to-protonmail e2e encryption makes a lot of sense. I just think protonmail-to-non-protonmail e2e needs a tooltip in the UI, and the option to opt out, potentially with the ability to opt out for specific email addresses. I wouldn't at all assume it would be on by default even IF I've been actively using PGP in my email clients, because it's something you usually have to manually set up yourself, very explicitly. That, and 99.9% of emails are plaintext.
Anyhoo, one thing I forgot which kind of negates the "what if I have multiple encryption keys tied to my email" is the fact that the opengpg keyserver does tie 1 email address to 1 key so you can't publish multiple encryption keys, fair enough. Git-crypt and file encryption, I set my associated email address to use +tags eg [email protected], so as far as protonmail etc are concerned there's only one key per logical email address.
-
Is it safe to commit a Terraform file to GitHub?
Apart from a few exceptions (like ansible for example, which supports native encryption), we moved away from encrypted secrets in git repos and use external things, depending on the platform (like parameter store / secrets manager for AWS or keyvault for Azure - both of these do track changes, btw), so I haven't looked for quite a while. Back in ye olden days we used https://github.com/AGWA/git-crypt which worked quite nicely, but the key management is cumbersome and it's based on GPG, which in itself is a bit of a light redish flag these days.
-
GitHub Private Repos Considered Private-Ish
How about encryption?
https://github.com/AGWA/git-crypt has been solid for me
-
Codeship jet alternative
You might want to check out git-crypt. It allows you to encrypt and decrypt files in a git repo without needing an external account, and supports .env files. That said, trying your hand at making one as a personal project could be a fun and rewarding experience!
-
Ask HN: Privacy-Conscious GitHub?
I hesitate to append this but one option I have seen thrown around and also debated is git-crypt [1] There are many caveats to doing this as any integrations that would need to read the file contents would also need to be able to decrypt the files so this may not be entirely useful and may add many levels of complexity and fragility.
[1] - https://github.com/AGWA/git-crypt
-
Vaults vs. Cryptomator? Security, Cloud syncing, integration?
The most interesting approach I've seen for this is https://github.com/AGWA/git-crypt
-
How can I Make this binary statically-linked?
Here is the Makefile.
I use git-crypt to encrypt files in git repositories quite a lot and I find that it doesn't work on RHEL-based distros because of some missing or out-of-date library. I need to build a statically linked binary.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
Store the Secrets in a repo using gitcrypt or another encryption tool.
-
I moved all my input files to a private repo and used it as a submodule
Consider using git-crypt for transparent encryption instead.
What are some alternatives?
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
git-secrets - Commit files with sensitive information like environment secrets safely encrypted in GitHub
gitignore - A collection of useful .gitignore templates
sops - Simple and flexible tool for managing secrets
git-lfs - Git extension for versioning large files
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
git-secret - :busts_in_silhouette: A bash-tool to store your private data inside a git repository.
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
github-cheat-sheet - A list of cool features of Git and GitHub.
dendron - The personal knowledge management (PKM) tool that grows as you do!
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere