Before you submit your app for review, you must read and accept the terms of the "GitHub Marketplace Developer Agreement." You'll accept the terms within your draft listing on GitHub. Once you've submitted your app, one of the GitHub Marketplace onboarding specialists will reach out to you with more information about the onboarding process, and review your app to ensure it meets these requirements:
GitHub 应用程序s should have a minimum of 100 installations.
OAuth 应用程序s should have a minimum of 200 users.
Apps must provide value to customers and integrate with the platform in some way beyond authentication.
Apps must be publicly available in GitHub Marketplace and cannot be in beta or available by invite only.
Apps cannot actively persuade users away from GitHub.
Marketing materials for the app must accurately represent the app's behavior.
Apps must include links to user-facing documentation that describe how to set up and use the app.
When a customer purchases an app and GitHub redirects them to the app's installation URL, the app must begin the OAuth flow immediately. For details, see "Handling new purchases and free trials."
Customers must be able to install your app and select repositories on both a personal and organization account. They should be able to view and manage those accounts separately.
- Apps that use GitHub logos must follow the "GitHub Logos and Usage" guidelines.
- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "Writing GitHub Marketplace listing descriptions."
- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "Writing GitHub Marketplace listing descriptions."
Apps will go through a security review before being listed on GitHub Marketplace. A successful review will meet the requirements and follow the security best practices listed in "Security review process." For information on the review process, contact firstname.lastname@example.org.
GitHub Marketplace 鼓励使用免费应用程序，这是提供开源服务的好方法。 如果您在 GitHub Marketplace 的外部上架了应用程序的付费版本，则您在 GitHub Marketplace 中上架该应用程序时，必须提供至少一个付费计划。 If you are listing a free app, you'll need to meet these requirements:
- Customers must be able to see that they have a free plan in the billing, profile, or account settings section of the app.
- When a customer cancels your app, you must follow the flow for cancelling plans.
To offer your app as a paid service, you'll need to meet these requirements to list your app on GitHub Marketplace:
- To sell your app in GitHub Marketplace, it must use GitHub's billing system. Your app does not need to handle payments but does need to use "GitHub Marketplace purchase events" to manage new purchases, upgrades, downgrades, cancellations, and free trials. See "Billing flows" to learn about how to integrate these events into your app. Using GitHub's billing system allows customers to purchase an app without leaving GitHub and pay for the service with the payment method already attached to their GitHub account.
- Apps must support both monthly and annual billing for paid subscriptions purchases.
- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "Setting a GitHub Marketplace listing's pricing plan."
- 取消从 GitHub Marketplace 购买的付费计划的客户必须被自动降级到该应用程序的免费计划（如果有）。 当客户取消 GitHub Marketplace 订阅时，GitHub 不会自动卸载应用程序，因此客户可以预期免费功能仍然有效。 强烈建议允许客户重新启用他们以前的计划。
- 如果您用以下格式提供升级 URL，客户必须能够从应用程序的 UI 升级：
- 固定费用和每单位计划的使用情况和剩余资源。 例如，如果定价计划是按单位计费，则应用程序的网站应显示已用单位和可用单位。