GitHub incident: ongoing issues with Actions, Issues and other Git operations
1–10 of 130 posts
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#2You will probably notice it also when trying to push a new branch:
`error: failed to push some refs to ` when using --set-upstream
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#3Does GitHub provide uptime stats? Seems very unreliable recently.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#4You will probably notice it also when trying to push a new branch: `error: failed to push some refs to ` when using --set-upstream
Indeed, I notice it when trying to push also:
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: fatal error in commit_refs
To github.com:acme/foo.git
! [remote rejected] HEAD -> acme/foo (failure)
error: failed to push some refs to 'github.com:acme/foo.git'Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#5Why don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#6Again?
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#7Why don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?
Enterprise says I have to use this unreliable garbage.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#8This is a monthly incident at this point. Maybe they have a rogue cron job??
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#9Why don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?
why particularly GitLab?
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#10Now pages too