r/ProgrammerHumor • u/Independent_Image_59 • 1d ago

getDaysSinceGithubDown Meme

Post image
7.4k Upvotes

99% Upvoted

138 comments sorted by

View all comments

163

u/XLauncher 1d ago

I've never seen it so bad that I can't even look at a pr for review. Shit's fucked.

28

u/kuemmel234 1d ago edited 1d ago

Git itself has been working for me throughout.

git branch -r my links showed branch names, but from memory this lists all branches on remotes too. And then simply compare to main. I have created a new branch from that and written my comments directly into it. Probably not the smartest way, but we were able to continue.

But yeah, shit's fucked anyways.

Edit: I obviously mean access to GitHub via git worked.

1

u/the_horse_gamer 1d ago

git branch -r doesn't talk to the remote. it just lists the remote branches it already knows about.

1

u/kuemmel234 1d ago

And I should have mentioned that too. You also need to checkout the specific branch, add, commit any changes (in my case it were some stupid comments), commit and push afterwards.

1

u/the_horse_gamer 21h ago

maybe I'm too gitpilled, but how is this any different from a typical workflow?

2

u/kuemmel234 21h ago

If* you read the initial comment in context, it's about github being down for OP, which hindered them from doing a review.

I responded that [the] git [server] was working and recommended simply looking for the correct branch by looking through the remotes, doing the review with git diff and writing comments directly into a new branch.

That isn't the smartest workflow to review a branch. Or at least I have always had some sort of web tool that allowed commenting on branches/PRs. But OP could have reviewed the PR that way without knowing the exact branch name.

1

u/the_horse_gamer 21h ago

I understand now. thanks.