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
I did the same job as before but I faced an error as follows.
Here is the message:
git.exe push --progress "origin" master:master
remote: Permission to seg/2016-ml-contest.git denied to ckjeong73.
fatal: unable to access 'https://github.com/seg/2016-ml-contest.git/': The requested URL returned error: 403 git did not exit cleanly (exit code 128) (3500 ms @ 2017-01-27 am 3:32:07)
Is anyone who met the same issue?
The text was updated successfully, but these errors were encountered:
It looks like you're trying to push to the SEG repo. You should push to
your own fork, then make pull request.
Do `git branch -a` to check which branch you're on.
Good luck, and let us know if it still doesn't work.
Cheers,
Matt
On Thu, Jan 26, 2017, 15:36 ckjeong73 ***@***.***> wrote:
I did the same job as before but I faced an error as follows.
Here is the message:
git.exe push --progress "origin" master:master
remote: Permission to seg/2016-ml-contest.git denied to ckjeong73.
fatal: unable to access 'https://github.com/seg/2016-ml-contest.git/':
The requested URL returned error: 403 git did not exit cleanly (exit code
128) (3500 ms @ 2017-01-27 am 3:32:07)
Is anyone who met the same issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#145>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABnS1KjZk1eOjOhoGkMCwox8UpaNu3AXks5rWPXTgaJpZM4LvDEA>
.
I did the same job as before but I faced an error as follows.
Here is the message:
git.exe push --progress "origin" master:master
remote: Permission to seg/2016-ml-contest.git denied to ckjeong73.
fatal: unable to access 'https://github.com/seg/2016-ml-contest.git/': The requested URL returned error: 403 git did not exit cleanly (exit code 128) (3500 ms @ 2017-01-27 am 3:32:07)
Is anyone who met the same issue?
The text was updated successfully, but these errors were encountered: