You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2023. It is now read-only.
I'm getting an error when trying to create a new feature. I am able to communicate with GitHub via vanilla GIT without any issues, so it seems that it is probablye related to HubFlow. Any suggestions on how to get around this?
After installating HubFlow per the readme and implementing the solution suggested in another issue (#114 (comment)), I get the following error:
fatal: remote repository is unavailable; are you offline?
Then after running chmod 0600 ~/.ssh/config, to fix this (as mentioned here: #75), I get the following error:
> git hf feature start fix-report-blank-filter-validation
Fetching origin
Switched to a new branch 'feature/fix-report-blank-filter-validation'
ssh_dispatch_run_fatal: Connection to 140.82.112.3 port 22: Operation timed out
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Push to 'origin' failed
I was able to work around this by adding the following to ~/.ssh/config:
User git
Hostname ssh.github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
Port 443
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm getting an error when trying to create a new feature. I am able to communicate with GitHub via vanilla GIT without any issues, so it seems that it is probablye related to HubFlow. Any suggestions on how to get around this?
After installating HubFlow per the readme and implementing the solution suggested in another issue (#114 (comment)), I get the following error:
Then after running
chmod 0600 ~/.ssh/config
, to fix this (as mentioned here: #75), I get the following error:I was able to work around this by adding the following to
~/.ssh/config
:The text was updated successfully, but these errors were encountered: