Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Public repository source code is visible to everyone; private repository is only accessible to authorized accounts. Visibility is not a license or a secret vault. Access should be granted with minimum privileges in software sales projects.
Turkey (Turkish)
Germany (German)
Worldwide (English)
Repository visibility: Private
Change repository visibility
Manage access
Invite a collaborator
Danger ZonePublic repository source code is visible to everyone; private repository is only accessible to authorized accounts. Visibility is not a license or a secret vault. Access should be granted with minimum privileges in software sales projects.
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 commit secrets to your private repo.
Meaning: Content may have become visible.
Possible cause: Incorrect visibility change.
Meaning: Private access is not secret management.
Possible cause: Incorrect security assumption.
Meaning: Role or branch policy is insufficient.
Possible cause: Read/Triage or protected branch.
Meaning: Usage right is undefined.
Possible cause: LICENSE yok.
Meaning: Fork/network behavior may be affected.
Possible cause: Public/private transition.
Meaning: The user is over-authorized.
Possible cause: Admin/team role.
Meaning: Access has not been revoked.
Possible cause: Offboarding eksik.
Meaning: Authorized person can retrieve local copy.
Possible cause: Normal Git behavior.
No records matching this expression were found.
gh repo view --json nameWithOwner,visibility,isPrivate,defaultBranchRefShows repository visibility.
gh api repos/OWNER/REPO/collaborators --paginate --jq '.[] | [.login,.permissions] | @tsv'Lists user and permissions.
gh api repos/OWNER/REPO/branches/main/protection 2>/dev/null || trueDisplays main protection settings
gh secret listLists names without showing secret values.
git remote -vDisplays the linked repository of the local copy.
git log -p --all | grep -Ei '(api[_-]?key|secret|token|password|BEGIN .*PRIVATE KEY)' | head -n 80Scans for possible secret traces in the past.
Repository Public, .env commitliRepository Private, `.env` ignore, secrets in GitHub SecretsCustomer to AdminGive the customer only the necessary repo and Read/Write role.Public, LICENSE yokPublic + uygun LICENSEproduction password in config.phpconfig.example.php + ENV + GitHub SecretsGit 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.