bfg-repo-cleaner
git-secret
Our great sponsors
bfg-repo-cleaner | git-secret | |
---|---|---|
53 | 22 | |
10,667 | 3,621 | |
- | - | |
1.5 | 5.7 | |
18 days ago | 7 days ago | |
Scala | Shell | |
GNU General Public License v3.0 only | MIT License |
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-secret
-
Gittuf – a security layer for Git using some concepts introduced by TUF
I've happily been using git-secret (https://sobolevn.me/git-secret/) for encrypting non-critical (i.e. non-production) secrets for a while now. It sounds like Gittuf will do a lot more than git-secret, but for the use case of encrypted files specifically, is there a significant different about with the approach that Gittuf has taken?
-
Ansible-based dotfiles with fancy nvchad-based neovim + tmux setup
Secrets inside the repo. All the credentials, ssh keys, VPN configs can be stored directly in the repo with support of the git secret. gpg key is optional: config works fine if it is not provided and secrets are not decrypted.
-
Modern Perl Catalyst: Docker Setup
You might notice that some of the environmental variables have funky values that look more like template placeholders. For example "SESSION_STORAGE_SECRET=${SESSION_STORAGE_SECRET}". That's because there's a .env file that contains those (you can see it in the root of the GitHub repository page. As a good practice I try to isolate anything that needs to be secret right off the top. So even though this is a development setup and would need work to turn it into a something suitable for production let's try to start off right not doing the wrong thing by hardcoding all our secrets into various files. At least now there's just one file to secure. And later on if you move to something really secure like Hashicorp's Vault product, or even something open source like git secret you won't have to hunt all over the place for the secrets to keep. Lets now look at the rest of the Catalyst application setup:
-
Terraform - How do you handle secrets?
Checkout git-secret. https://git-secret.io/
-
[2022][Friendly Reminder] Don't commit your input files to Git
There‘s plugins like https://github.com/AGWA/git-crypt or https://git-secret.io that you can use to encrypt the files for yourself, so that they are available on multiple machines to you
- how to automate the sharing .env file with the team?
-
How to hide changes in GitHub repository from the public?
If you really want to have private repositories in GitHub, you will need to set up something like https://git-secret.io on top of git.
- Using GNU Stow to manage your dotfiles (2012)
-
Would it be worth using a secrets management system?
If you want a low config solution and not scared of gpg, https://git-secret.io/
-
git-secret vs Mozilla SOPS?
Hey guys, so I'm using git-secret as of now. Just stumbled across Mozilla SOPS today and finding it interesting. Which one you guys recommend and why? Advantages and disadvantages of each? I think SOPS is more robust and stable since it is being maintained by a large organization? Please correct me if I'm wrong. Help is appreciated.
What are some alternatives?
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
sops - Simple and flexible tool for managing secrets
gitignore - A collection of useful .gitignore templates
vaultwarden - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
git-lfs - Git extension for versioning large files
secret - Share Secrets securily
github-cheat-sheet - A list of cool features of Git and GitHub.
Blackbox - Safely store secrets in Git/Mercurial/Subversion
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
git-crypt - Transparent file encryption in git
passff - zx2c4 pass manager extension for Firefox, Chrome and Opera