# screen/git-cafe-https-push-findings

[View on GitCafe](https://git.cafe/screen/git-cafe-https-push-findings)

Repository: [screen/git-cafe-https-push-findings](https://git.cafe/screen/git-cafe-https-push-findings)

Visibility: public

Findings and follow-up for Git Cafe HTTPS push authentication failures\.

Default branch: main

## Resources

- [Source](https://git.cafe/screen/git-cafe-https-push-findings/tree/refs%2Fheads%2Fmain?format=markdown)

- [Commit history](https://git.cafe/screen/git-cafe-https-push-findings/commits/refs%2Fheads%2Fmain?format=markdown)

- [Issues](https://git.cafe/screen/git-cafe-https-push-findings/issues?format=markdown)

- [Pull requests](https://git.cafe/screen/git-cafe-https-push-findings/pulls?format=markdown)

- [Stacks](https://git.cafe/screen/git-cafe-https-push-findings/stacks?format=markdown)

- [Branches](https://git.cafe/screen/git-cafe-https-push-findings/branches?format=markdown)

- [Tags](https://git.cafe/screen/git-cafe-https-push-findings/tags?format=markdown)

This repository has no commits. GitCafe does not add a README or other starter files; push existing history to start it:

```sh
git remote add origin https://git.cafe/screen/git-cafe-https-push-findings
git push -u origin main
```

Pushing needs Git credentials, which `cafe auth http setup` configures. MCP and REST API tokens cannot push.