GitRelease 🚀

Your private Play Store for QA, built on top of GitHub Releases.

GitRelease exists to solve one painfully common problem:
developers manually sharing APKs over Slack, WhatsApp, Drive, or email for testing.

This app removes that entire workflow.

GitRelease fetches release data directly from GitHub repositories, shows all Release and Pre-release APKs, and lets testers download and install builds instantly — straight from GitHub.

Think of it as a secondary Play Store, but only for QA and internal testing.

---

What Problem Does This Solve?

• No more APKs shared in chat threads
• No more “latest build?” messages
• No more guessing which APK is correct
• No more manual distribution for testers

If the APK is attached to a GitHub Release → GitRelease can fetch and install it.

---

Core Features

📦 GitHub Releases as a Distribution Channel

• Fetches repository details directly from GitHub
• Lists Release and Pre-release tracks separately
• Displays all APK assets attached to a release
• One-tap download and install

🧪 Built for QA & Internal Testing

• Perfect for:
  • QA teams
  • Internal testers
  • Dogfooding builds
• Acts like a private Play Store, without Play Store delays or approvals

🔐 Public & Private Repository Support

• Works with public repositories out of the box
• Supports private repositories using a GitHub Personal Access Token
• Token scope required: repo
• Token is used only to fetch release metadata
• No token is stored remotely

🔄 No Manual Sharing, Ever Again

• Developers push a release → testers see it instantly
• No Slack uploads
• No WhatsApp APK chaos
• No Drive links expiring

---

Safety, Privacy & Transparency (No Fine Print)

Let’s be very clear:

• ✅ No Firebase
• ✅ No analytics
• ✅ No logging
• ✅ No tracking
• ✅ No background uploads
• ✅ No hidden API calls

The app:

• Talks only to GitHub’s official APIs
• Makes read-only requests
• Does not collect, store, or transmit user data

This project is 100% open source.
There is nothing to hide — you can audit every line of code yourself.

---

Open Source by Design 🧩

GitRelease is fully open source so teams can:

• Trust what the app does
• Fork it for internal use
• Modify it for company-specific workflows
• Self-host if needed

If something looks suspicious, it isn’t — you can verify it in the code.

---

How It Works (High Level)

1. Enter a GitHub repository (owner/repo)
2. (Optional) Add a GitHub Personal Access Token for private repos
3. App fetches:
   • Repository metadata
   • Releases & pre-releases
   • APK assets
4. Select a build → download → install

---

Using Private Repositories (GitHub Personal Access Token)

GitRelease can access private repositories if you provide a GitHub Personal Access Token. This is optional and only required for private repos.

How to Generate a Personal Access Token

1. Open GitHub and go to Settings
2. Navigate to Developer settings
3. Click Personal access tokens
4. Select Tokens (classic)
5. Click Generate new token → Generate new token (classic)
6. Add a note (e.g. GitRelease QA Access)
7. Set an expiration date (recommended)
8. Under Select scopes, enable only:
   • repo
9. Generate the token and copy it

Important:

• Use Classic tokens only (Fine-grained tokens are not supported)
• Grant repo access only — nothing else is required
• The token is used only to read repository and release data
• The token is never logged, tracked, or shared

---

Demo & Screenshots

🎥 Video Demo

Record_2026-02-02-22-49-49_b783bf344239542886fee7b48fa4b892.mp4

📱 Screenshots

---

Who Is This For?

• Android developers tired of manual APK sharing
• QA teams that need fast access to builds
• Startups without Play Store internal testing pipelines
• Anyone using GitHub Releases as their source of truth

---

TL;DR

• GitHub Releases → APK distribution
• Zero tracking
• Zero data collection
• Fully open source
• Built specifically for QA

Ship once. Test everywhere. Stop sharing APKs manually.