Drag and drop in the terminal is certainly cool but I've been recently getting into lazy git, also a terminal git client and it's workflows are all keyboard driven. It presents a mental model that is much easier to deal with than standard git terminal command line. https://github.com/jesseduffield/lazygit. - Source: Hacker News / 13 days ago

You can learn the necessary information about usage and key combinations on the Lazygit official website Github - Lazygit. - Source: dev.to / 13 days ago

Lazygit (https://github.com/jesseduffield/lazygit) is enlightenmentware for me. It helps me navigate Git commands I forget all the time, like using the reflog to undo things, custom patches, or rebase --onto. It makes working with Git a lot more fun, and I giggle like a little child whenever one of the weirder things work out again. - Source: Hacker News / 27 days ago

Sounds like something comparable to LazyGit. https://github.com/jesseduffield/lazygit. - Source: Hacker News / about 1 month ago

I've started to en ntegrate lazygit into my workflow. It's quite easy to work with and I use git in a more powerfull way. My main problem is finding the way in all hotkeys. https://github.com/jesseduffield/lazygit?tab=readme-ov-file#.... - Source: Hacker News / 2 months ago

Git Secret is an essential bash tool for developers and DevOps professionals, offering a robust solution for secret management within a Git repository. This open-source tool effectively encrypts sensitive files and data, ensuring that confidential information like passwords, keys, and credentials are securely stored in the repository. - Source: dev.to / 5 months ago

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. Source: 8 months ago

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... - Source: dev.to / 11 months ago

There are a number of possible solutions: https://github.com/spwhitton/git-remote-gcrypt https://github.com/AGWA/git-crypt https://github.com/sobolevn/git-secret Most people who self-host a Git repository are fine with just transport-level encryption (TLS). - Source: Hacker News / almost 2 years ago

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. Source: almost 2 years ago