BREAKING: GitHub MINOR 🔴 Pull Requests & Issues Down — Workarounds Inside

GitHub experiencing partial disruption affecting PRs and Issues. Immediate workarounds for indie hackers and teams.

BREAKING: GitHub Experiencing Pull Request & Issue Disruption

Status: Investigating | Severity: Minor | Impact: Partial

Last Updated: Monitor [GitHub Status Page](https://www.githubstatus.com) for real-time updates.

---

What's Down & Who's Affected

GitHub is currently experiencing degraded performance on Pull Requests and Issues functionality. This affects:

Creating, viewing, or updating pull requests

Opening, filtering, or searching issues

PR/Issue notifications and webhooks (intermittent)

Some project board operations

Who's impacted: Teams relying on active PR reviews, issue triage workflows, and automated CI/CD that depends on PR status updates.

Code commits and pushes: Still operational. Your repository data is safe.

---

Immediate Workarounds — Do These NOW

For Pull Requests

1. Pause code review cycles temporarily. Use email/Slack to notify reviewers of pending PRs. 2. Use the Git CLI for local operations: ```bash git log --oneline origin/main..HEAD # See your commits waiting for review ``` 3. Continue pushing commits — they're queuing successfully. PRs will sync once service recovers.

For Issues

1. Document blockers locally in a markdown file or Notion until GitHub stabilizes. 2. Use GitHub CLI (installed locally) to query issues: ```bash gh issue list --state open ``` 3. Avoid bulk operations — wait for stability before mass label changes or migrations.

For Teams & CI/CD

1. Don't retry deployments waiting on PR status checks — they'll fail intermittently. 2. Use branch protection bypass (admins only) if you have critical hotfixes, but log the decision. 3. Check webhook delivery in repo settings → Developer settings → Webhooks (manual retry after recovery).

---

How to Check If Your Project Is Affected

Quick test: 1. Go to your repo → "Pull requests" tab 2. Try clicking "New pull request" or viewing an existing PR 3. If you see timeouts, 500 errors, or "loading" spinners >30 seconds = you're affected

For issues:

Navigate to Issues tab and try filtering by label or assignee

Slow response or blank results = disrupted

Check your CI/CD:

Review recent workflow runs in Actions tab

Pending checks may not update until service recovers

---

Alternative Tools to Consider (Temporary Bridge)

For PR review and issue tracking *during* outages:

Gitea (self-hosted, free) — full Git + PR/Issue support

Gitlab.com — cloud alternative with native PR/Issue tools

Plane.so — lightweight issue tracking, GitHub integration

Linear — fast issue tracking (syncs with GitHub)

Slack/Discord threads — temporary communication for blockers

*Note:* Most indie hackers should stick with GitHub and ride this out — it's typically resolved in <2 hours.

---

Monitor Recovery

Official source (refresh every 5 min):

[GitHub Status Page](https://www.githubstatus.com)

Subscribe to updates: 1. Visit status.github.com → Click "Subscribe to updates" 2. Enable email/SMS notifications 3. Follow [@githubstatus](https://twitter.com/githubstatus) on Twitter

Test recovery yourself:

Once status shows "Investigating → Identified → Monitoring," try creating a test PR in a dummy repo

If it succeeds, you're good to resume normal workflows

---

Bottom Line

This is a partial outage — not a data loss event. Your code is safe. Continue pushing commits, communicate blockers via email/chat, and wait for GitHub to stabilize. Most indie hacker workflows can pause PR review for 1-2 hours without major impact.

Bookmark this. Reference again if symptoms persist.