Conversation
|
Caution Review failedThe pull request is closed. WalkthroughBumped product/version metadata to 1.0.0, added a conductor setup script and toolkit setup/run scripts (with a dependency check), added privacy and Chrome Web Store release docs, updated README, and removed two outdated docs. No runtime API or permission changes beyond documentation and scripts. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR prepares the extension for a v1.0.0 release by bumping the version, adding Chrome Web Store release documentation, adding a privacy policy, wiring in Conductor setup/run scripts, and enriching the main README with architecture, workflow, and testing details.
Changes:
- Bumped the extension and package version from 0.5.0 to 1.0.0 and aligned build/test tooling around Bun, Biome, and GitHub Actions.
- Added Chrome Web Store release documentation, privacy policy, and marketing screenshots, and removed the older quick-release guide and raw requirements note.
- Introduced Conductor
setup/runscripts to install dependencies and build the extension via Bun.
Reviewed changes
Copilot reviewed 10 out of 14 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
toolkit/Conductor/setup.sh |
New setup script to install dependencies with Bun and build the extension for Conductor-driven workflows. |
toolkit/Conductor/run.sh |
Updated run script to guard against missing dependencies and invoke the Bun build. |
package.json |
Bumped project version to 1.0.0 and ensured scripts align with the documented Bun-based build/test pipeline. |
manifest.json |
Updated Chrome extension metadata to version 1.0.0 and renamed the published extension to “Clean Autofill”. |
docs/requirements/Requirements.md |
Removed the original high-level requirements brief now superseded by richer documentation. |
docs/chrome-web-store-release.md |
Added a full Chrome Web Store release guide describing OAuth setup, GitHub secrets, workflow behavior, and tag strategy. |
docs/Screenshots/Clean-Autofill-Screenshot-1.png |
Added a marketing/product screenshot referenced from the README. |
docs/README.md |
Greatly expanded the documentation with feature overview, tech stack, architecture, build/test commands, file structure, and dev workflow. |
docs/QUICK_RELEASE_GUIDE.md |
Removed the old quick release guide in favor of the new, more detailed Chrome Web Store release doc. |
docs/PRIVACY.md |
Added a privacy policy describing local-only processing, minimal data storage, and required permissions. |
conductor.json |
Wired Conductor to use the new setup script and existing run script in toolkit/Conductor. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "manifest_version": 3, | ||
| "name": "Clean-Autofill", | ||
| "version": "0.5.0", | ||
| "name": "Clean Autofill", |
There was a problem hiding this comment.
The extension name in manifest.json ("Clean Autofill") no longer matches the name used elsewhere in the repo (e.g., "Clean-Autofill" in docs and repo URL). To avoid user confusion and potential Chrome Web Store listing inconsistencies, it would be better to standardize the product name across manifest.json, docs, and store/repo references.
| "name": "Clean Autofill", | |
| "name": "Clean-Autofill", |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/PRIVACY.md`:
- Line 53: The bare URL in the PRIVACY.md sentence "If you have questions about
this privacy policy, please visit
https://github.com/ZAAI-com/Clean-Autofill/issues." should be formatted as a
Markdown link; replace the raw URL with a markdown link like [Clean-Autofill
issues](https://github.com/ZAAI-com/Clean-Autofill/issues) (or similar
descriptive text) so the link is accessible and renders properly in Markdown.
🧹 Nitpick comments (3)
toolkit/Conductor/run.sh (1)
1-10: Consider addingset -efor consistency with setup.sh.The dependency check is a good addition. For consistency with
setup.shand to ensure the script exits on any unexpected errors, consider addingset -eafter the shebang.♻️ Suggested improvement
#!/bin/bash # Conductor run script - builds the Chrome Extension + +set -e # Check if dependencies are installeddocs/chrome-web-store-release.md (1)
94-96: Consider adding a language specifier to the fenced code block.The code block containing the OAuth URL lacks a language specifier. Adding
textwould satisfy linting and clarify this is not executable code.📝 Suggested fix
-``` +```text https://accounts.google.com/o/oauth2/auth?response_type=code&scope=https://www.googleapis.com/auth/chromewebstore&client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost ```docs/README.md (1)
54-54: Remove hardcoded test counts and coverage percentages.The documentation contains hardcoded metrics that will quickly become stale:
- "119 tests" appears at lines 54 and 222
- "98%+ line coverage" at line 224
These numbers require manual updates each time tests are added or removed, creating maintenance overhead and potential inaccuracies. Consider either:
- Removing the specific numbers entirely (e.g., "Run tests with DOM support")
- Adding a note like "(count may vary)"
- Using a badge or automated metric if possible
📝 Suggested documentation updates
-# Run tests (119 tests with DOM support) +# Run tests with DOM support bun test src/ # Run tests in watch mode-bun test src/ # Run all 119 tests +bun test src/ # Run all tests bun run test:watch # Watch mode -bun run test:coverage # Coverage report (98%+ line coverage) +bun run test:coverage # Generate coverage reportAlso applies to: 222-222, 224-224
manuelgruber
changed the title
Summary
Bump Clean-Autofill to v1.0.0 with comprehensive documentation and Chrome Web Store preparation. Enhanced README with feature highlights, use cases, and architecture overview. Added privacy policy, Chrome Web Store release guide with setup instructions, and product screenshots. Improved Conductor integration with new setup script.
Changes
Summary by CodeRabbit
New Features
Documentation
Chores
Documentation (Removed)