Search Results for "safety"

...Supports workflows with multiple release branches, e.g. only delete branches that have been merged to all of master, dev and staging. Quick interactive configuration. Provider agnostic: Works with GitHub, GitLab, Gitea and any other Git hosting. Takes safety seriously. Deletion is a sharp knife that requires care. While git reflog would have your back in most cases, git-delete-merged-branches takes safety seriously. git push is used with --force-with-lease so if the server and you have a different understanding of that branch, it is not deleted. There is no use of os.system or shell code to go wrong.

Checkout v7 is the official GitHub Action for checking out repository code inside a GitHub Actions workflow. It places the selected repository under the workflow workspace so build, test, lint, release, or deployment steps can access the files. By default, it fetches only one commit for the ref or SHA that triggered the workflow, but it can also fetch full branch and tag history. The action supports checking out different repositories, private repositories, pull request commits, submodules,...

A script to configure transparent encryption of sensitive files stored in a Git repository. Files that you choose will be automatically encrypted when you commit them, and automatically decrypted when you check them out. The process will degrade gracefully, so even people without your encryption password can safely commit changes to the repository's non-encrypted files. transcrypt protects your data when it's pushed to remotes that you may not directly control (e.g., GitHub, Dropbox clones,...