@@ -50,7 +50,7 @@ Use `.env.local` for local secrets. Keep `.env.local` and any real token-bearing
|
||||
- Add Issue is enabled only when the active tab's base URL is already in the URLs list and has a linked Gitea repo. The issue form must show the target repo, capture visible-tab screenshots, accept Gitea-friendly file attachments, and include `Chrome profile: Silma` in created issue bodies.
|
||||
- Newly created issues must be created with the `Change Request` label.
|
||||
- If the Ready checkbox is checked, create the issue first, upload screenshots/files as issue assets second, and apply the `ready` label last.
|
||||
- The Add Issue view also lists existing issues for the linked Gitea repo. Selecting an issue must show a comment form that can add text, take additional screenshots, attach files, upload those files as issue assets, and submit a Gitea comment with attachment links.
|
||||
- The Add Issue view also lists existing issues for the linked Gitea repo. Selecting an issue must show the original description, issue attachments, and comment chain, followed by a comment form that can add text, take additional screenshots, attach files, upload those files as issue assets, and submit a Gitea comment with attachment links.
|
||||
- Existing issue rows must allow applying the `ready` label and deleting the issue. Deletion must require user confirmation.
|
||||
- Keep the Add Issue view dense; do not show the redundant view header title/description inside this view, and keep the Ready checkbox label short.
|
||||
- The extension requests `activeTab` and `<all_urls>` host permission so screenshots can be captured from the current Chrome tab even after the side panel has stayed open across tab changes.
|
||||
|
||||
Reference in New Issue
Block a user