[PR #799] [CLOSED] Add PGYER upload app action to Deployment #9433

Closed
opened 2026-05-31 06:26:23 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/sdras/awesome-actions/pull/799
Author: @shishirui
Created: 5/20/2026
Status: Closed

Base: mainHead: add-pgyer-upload-app-action


📝 Commits (1)

  • 7f4ed8f Add PGYER upload app action to Deployment

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

What

Adds the official PGYER upload app action to the Deployment section (end of category, per contributing guidelines).

Why this belongs here

  • Vendor-official action — published and maintained by PGYER, not a third-party wrapper.
  • Real, published Marketplace action with a working action.yml — plug-and-play in any workflow.
  • Fills a real gap in the list. The Deployment section already includes deploy targets for VS Code Marketplace, Cocoapods, Netlify, Shopify, Cloudflare, Anchor.fm, Spotify, etc. — but no mobile beta-distribution target. This action lets iOS/Android teams ship .ipa/.apk builds to testers directly from their workflow.
  • PGYER has operated since 2014 (12+ years) and is one of the most widely used mobile beta-distribution platforms in China (analogous to TestFlight / Firebase App Distribution), serving hundreds of thousands of mobile developers.

Guidelines checklist

  • Submitted at the end of the relevant category (Deployment).
  • Short description, one line, no bold/italics.
  • Searched existing entries — not a duplicate (no "pgyer" hits in current README).
  • Title Case used.
  • Format [List Name](link).
  • Useful PR title (not "Update readme.md").
  • Commit body links to the repository.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/sdras/awesome-actions/pull/799 **Author:** [@shishirui](https://github.com/shishirui) **Created:** 5/20/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-pgyer-upload-app-action` --- ### 📝 Commits (1) - [`7f4ed8f`](https://github.com/sdras/awesome-actions/commit/7f4ed8f7a54c8bbbe05c053d44ace39a9fa23e2b) Add PGYER upload app action to Deployment ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description ## What Adds the official **PGYER upload app action** to the Deployment section (end of category, per contributing guidelines). - Entry: `[Upload iOS/Android Apps to PGYER Beta Distribution](https://github.com/PGYER/pgyer-upload-app-action)` - Marketplace: https://github.com/marketplace/actions/this-action-uploads-an-application-file-to-pgyer - Repository: https://github.com/PGYER/pgyer-upload-app-action ## Why this belongs here - **Vendor-official action** — published and maintained by [PGYER](https://github.com/PGYER), not a third-party wrapper. - **Real, published Marketplace action** with a working `action.yml` — plug-and-play in any workflow. - **Fills a real gap in the list.** The Deployment section already includes deploy targets for VS Code Marketplace, Cocoapods, Netlify, Shopify, Cloudflare, Anchor.fm, Spotify, etc. — but no mobile beta-distribution target. This action lets iOS/Android teams ship `.ipa`/`.apk` builds to testers directly from their workflow. - PGYER has operated since 2014 (12+ years) and is one of the most widely used mobile beta-distribution platforms in China (analogous to TestFlight / Firebase App Distribution), serving hundreds of thousands of mobile developers. ## Guidelines checklist - [x] Submitted at the end of the relevant category (Deployment). - [x] Short description, one line, no bold/italics. - [x] Searched existing entries — not a duplicate (no "pgyer" hits in current README). - [x] Title Case used. - [x] Format `[List Name](link)`. - [x] Useful PR title (not "Update readme.md"). - [x] Commit body links to the repository. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-31 06:26:23 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-actions#9433