Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Push branch protection, ruleset, PR/CI requirement, or 100 MB single file limit, or secret push protection may be denied.
Turkey (Turkish)
Germany (German)
Worldwide (English)
remote: error: GH013: Repository rule violations
protected branch hook declined
File exceeds 100 MB
Push cannot contain secretsPush branch protection, ruleset, PR/CI requirement, or 100 MB single file limit, or secret push protection may be denied.
Do not perform a reset or force operation without seeing `git status`, active branch, remote and last commits.
Check that the HTTPS credential, SSH key, remote URL and GitHub account are correct.
Leave a rollback point with a commit or backup branch before fetching, merging or rebase.
Use feature branch flow instead of bypassing protected branch, review, CI and secret scanning rules.
Don't close the Ruleset so that it can only push.
Meaning: Does not comply with the ruleset.
Possible cause: PR, signature, status, or file rule.
Meaning: Direct branch push is prohibited.
Possible cause: Main protection.
Meaning: The blob limit is exceeded.
Possible cause: ZIP, backup or binary.
Meaning: Push protection secret buldu.
Possible cause: Token/key committed.
Meaning: CI is not successful
Possible cause: Test/lint error.
Meaning: No commit signature.
Possible cause: Ruleset signature requirement.
Meaning: Push is too large.
Possible cause: Large history/binary.
Meaning: Branch history rewrite yasak.
Possible cause: Protection policy.
No records matching this expression were found.
git rev-list --objects --all | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' | awk '$1=="blob" {print $3,$4}' | sort -nr | head -n 30List largest Git blobs.
git lfs env && git lfs ls-filesDisplays Git LFS status.
gh api repos/OWNER/REPO/rulesets --paginate 2>/dev/null || trueDisplays repository rulesets.
git log -p --all | grep -Ei '(api[_-]?key|token|secret|password|BEGIN .*PRIVATE KEY)' | head -n 100Scans possible secret signatures.
git log --show-signature -n 5Shows the last commit signatures.
git status --short --branch && git branch -vvShows the active branch/upstream status.
git push origin maingit switch -c feature/duzeltme
git push -u origin HEAD
gh pr create --base main --fillgit add backup.zip
git pushgit rm --cached backup.zip
echo "backup*.zip" >> .gitignore
git commit --amendgit add video.mp4git lfs track "*.mp4"
git add .gitattributes video.mp4
git commit -m "Video LFS"Delete the token from the file and push itRevoke the Token, clean from history, use GitHub Secrets/ENV.Git for Windows, PowerShell, Git Bash, and VS Code Source Control can be used together.
HTTPS credential manager; SSH is available for long-term and multi-account development environments.
Repository role, protected branch, Pull Request, and CI policies must be managed together.
For easy start, HTTPS and Git Credential Manager are suitable for automation and multiple account; SSH is suitable for automation and multiple account.
In Git operations, account password is replaced with PAT, credential manager, GitHub CLI, or SSH.
Use only to restrict access; secret, password, private key, and customer data should not be committed again.
Only use in a consciously rewritten personal feature branch and preferably with `--force-with-lease`.
Branch protection is required if necessary; also provides review and secure main history in single-person projects.
Replace OWNER, REPO, branch, URL, and file values with your project and verify first with `git status` and `git remote -v`.
Usually no. Deleting the `.git` folder can cause loss of commit history, branch, and remote information.
We examine Windows, VS Code, Git Bash, SSH, private repository, protected branch, merge conflict and GitHub Actions problems with a secure Git flow.