Fetching and Pushing to github through a firewall
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
could be useful for: @2DegreesInvesting/banks
context: while working remotely, I was unable to access my remote repositories (couldn't fetch, clone push etc. to upstream or origin). Initially I thought this was an issue with my git config, so I reset my SSH key, and double checked all my credentials to no avail.
turns out the bank's firewall blocks the ssh protocol entirely, and port 22 was deliberately blocked:
the fix: change your remotes from SSH to HTTPS (aka make sure all your upstreams, origins etc are expressed as https://github.com/username/repo.git instead of git@github.com:username/repo.git).
This can be done manually, for the open repo, by editing the local config:
git config --local -e
and ensuring all urls are in https format.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue body and its linked Stack Overflow answer, then inspect how resources are recorded in this repository. Document the firewall-related SSH failure and the HTTPS remote workaround, with the relevant git config command, so the guidance is available to remote contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100