extensiondev
GitHub App
extensiondev
GitHub App
Integrate extension.dev with your GitHub projects for automatic deployment and cross-browser distribution of your browser extension. For every pull-request, a deployment link is available with the latest changes of the build artifact, ready for distribution.
Visualize extension deployments for every new pull-request with zero-configuration, or configure it to also support automatic distribution of your extension across the multiple marketplaces.
Build once, distribute everywhere.
✅ Automatic Deployments on Push
When you push code to your repository, webhook-triggered deployments can be initiated to build and deploy your browser extension. This deployment guide supports building browser extensions for Chrome, Firefox, and Edge.
How it works:
- Webhook Triggers: Deployments are triggered via webhook events to the CI/CD pipeline
- Build Process: Each deployment includes a complete build and validation process for browser extensions
- Status Updates: Deployment status updates are provided through GitHub's deployment API
- Build History: Previous builds remain available for reference and promotion
Benefits:
- CI/CD Integration: Automated build and deployment pipeline for browser extensions
- Quality Assurance: Automated testing and validation during the build process
- Team Collaboration: All team members can see deployment status and build logs
- Version Control: Complete build history tied to your git commits
🧩 Preview Deployments for Pull Requests
When you create a Pull Request, preview deployments can be generated to test your browser extension changes before merging to the main branch. This deployment guide supports creating isolated preview environments for testing.
Preview Deployment Features:
- Unique URLs: Each deployment can get its own preview URL for testing
- Isolated Environment: Changes are tested in isolation without affecting production
- Team Review: Share preview URLs with team members for code review
- Build Validation: Extension builds are validated during the deployment process
- Status Integration: Deployment status can be posted to PR comments when configured
Workflow:
- Create PR: Push changes to a feature branch and create a Pull Request
- Trigger Deployment: Preview deployment is triggered via webhook or manual action
- Testing: Test your extension using the preview URL
- Review: Team members can review and test the changes
- Merge: Once approved, merge to trigger production deployment
Preview URL Format:
https://your-extension-preview.extension.land/sha/browser/
🔐 Repository Permissions
The extension.dev app requires specific permissions to provide the best possible deployment experience for your browser extension project. Here's what each permission allows the app to do:
Repository Permissions
Repository permissions allow the app to deploy your browser extension and provide a seamless development experience.
| Permission | Read | Write | Description |
|---|---|---|---|
| Administration | Yes | Yes | Allows the app to create repositories on behalf of the connected user or organization for new extension projects. |
| Checks | Yes | Yes | Allows the app to add automated checks and validations against source code during the deployment process. |
| Contents | Yes | Yes | Allows the app to fetch and write source code for new project templates for the connected user or organization. |
| Deployments | Yes | Yes | Allows the app to synchronize deployment status between GitHub and the deployment infrastructure. |
| Pull Requests | Yes | Yes | Allows the app to create deployments for each Pull Request (PR) and comment on those PR's with status updates. |
| Issues | Yes | Yes | Allows the app to interact with Pull Requests as with the Pull Requests permissions due to GitHub requiring both for access. |
| Metadata | Yes | No | Allows the app to read basic repository metadata to provide a detailed dashboard. |
| Web Hooks | Yes | Yes | Allows the app to react to various GitHub events. |
| Commit Statuses | Yes | Yes | Allows the app to synchronize commit status between GitHub and the deployment platform. |
Organization Permissions
Organization permissions allow the app to offer an enhanced experience through information about the connected organization.
| Permission | Read | Write | Description |
|---|---|---|---|
| Members | Yes | No | Allows the app to offer a better team onboarding experience. |
User Permissions
User permissions allow the app to offer an enhanced experience through information about the connected user.
| Permission | Read | Write | Description |
|---|---|---|---|
| Email addresses | Yes | No | Allows the app to associate an email with a GitHub account. |
Permission Usage
This deployment guide uses the permissions above to provide you with the best possible deployment experience for your browser extension development workflow. If you have any questions or concerns about any of the permission scopes, please contact our support team.
Security Considerations
- Minimal Permissions: This deployment guide only requests the permissions necessary for deployment and collaboration
- Read-Only Access: Most permissions are read-only to ensure your code security
- Webhook Security: Webhooks are secured and validated to prevent unauthorized access
- Data Protection: All repository data is handled according to security best practices
Developer
extensiondev is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.
Report abuse