Repository navigation
Add basic CI for project #48
Description
Task Summary
Build the GitHub Actions workflow responsible for automatically publishing the extension to the Chrome Web Store. This task includes setting up the necessary secrets and signing process.
Implementation Notes
The workflow should be triggered by a git tag (e.g., v2.0.1).
It needs to use a pre-existing GitHub Action for publishing to the Chrome Web Store (e.g., chrome-webstore-upload-action).
Store the Client ID, Client Secret, and Refresh Token as GitHub Secrets.
The workflow should create a .zip file of the extension, sign it, and upload it.
Checklist
- Create and configure a new GitHub Actions workflow file.
- Add secrets for the Chrome Web Store API credentials to the repository.
- Configure the workflow to run on a tag push.
- Implement the build and zip step.
- Implement the publishing step using the appropriate action.
- Test the pipeline with a manual trigger to ensure it works correctly.
Activity
anupsingh244 commentedon Sep 15, 2025
Decided to move away from automated CD publishing for now. We will be handling Chrome Extension publishing manually instead of setting up a full CI/CD pipeline.
The reasoning is:
• Manual publishing provides better control during the Beta phase and allows us to verify each build carefully before release.
• Chrome Web Store publishing flow often requires human validation (assets, screenshots, description updates), which limits the benefit of full automation.
• This approach reduces setup overhead and avoids managing sensitive credentials in GitHub for now.
We can revisit automation once the extension is stable in production and the publishing workflow becomes repetitive enough to justify CI/CD.
Closing this task accordingly.
[-]Implement CI/CD for Automated Beta Publishing[/-][+]Add basic CI for project[/+]