From 79ac4589264782bf1af42e8bbc4680898f90352d Mon Sep 17 00:00:00 2001 From: legend91019 <15853153143@163.com> Date: Sun, 18 Oct 2026 18:15:47 +0800 Subject: [PATCH 1/4] feat(process): add structured issue forms for bug reports and feature requests Add GitHub Issue Forms under .github/ISSUE_TEMPLATE/: - bug_report.yml: structured collection of version, OS/arch, install method, browser/extension version, exact command/API, reproduction steps, expected/actual behavior, sanitized logs, and regression tracking. - feature_request.yml: structured problem statement, proposed solution, alternatives considered, affected surfaces, and compatibility considerations. - config.yml: disable blank issues and route security reports to GitHub Security Advisories and questions to Discussions. Fixes #462 --- .github/ISSUE_TEMPLATE/bug_report.yml | 141 +++++++++++++++++++++ .github/ISSUE_TEMPLATE/config.yml | 8 ++ .github/ISSUE_TEMPLATE/feature_request.yml | 67 ++++++++++ 3 files changed, 216 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 00000000..d1765dc7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,141 @@ +name: Bug Report +description: Report an issue or unexpected behavior in BrowserSkill. +title: "[Bug]: " +labels: ["bug"] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to report an issue! + Please fill out this form as completely as possible to help us diagnose and resolve the issue quickly. + - type: checkboxes + id: prerequisites + attributes: + label: Prerequisites + description: Please verify the following before submitting. + options: + - label: I have searched existing [open and closed issues](https://github.com/Tencent/BrowserSkill/issues) to ensure this is not a duplicate. + required: true + - label: I have verified that all sensitive data (passwords, tokens, API keys, private URLs, personal info) have been redacted from logs and snippets. + required: true + - label: This is a bug report and not a security vulnerability (see our [Security Advisories](https://github.com/Tencent/BrowserSkill/security/advisories/new)). + required: true + - type: input + id: version + attributes: + label: BrowserSkill Version or Commit + description: Output of `bsk --version` or git commit SHA (e.g. `0.3.3`, `d9a78ae`). + placeholder: e.g., 0.3.3 + validations: + required: true + - type: dropdown + id: os + attributes: + label: Operating System + description: The OS where `bsk` is running. + options: + - Windows 11 + - Windows 10 + - macOS (Apple Silicon) + - macOS (Intel) + - Linux (x86_64) + - Linux (aarch64) + - Other (specify in description) + validations: + required: true + - type: input + id: arch + attributes: + label: OS Details and Architecture + description: Exact OS release and CPU architecture (e.g., Ubuntu 24.04 x86_64, Windows 11 23H2 x64, macOS 15.0 arm64). + placeholder: e.g., Windows 11 Build 22631 x64 + validations: + required: true + - type: dropdown + id: install_method + attributes: + label: Installation Method + description: How was BrowserSkill installed? + options: + - Official installer script (AGENT_INSTALL.md) + - Prebuilt binary release from GitHub Releases + - Built from source (`cargo build`) + - Package manager (e.g. brew / winget / npm / other) + - Other + validations: + required: true + - type: input + id: browser_version + attributes: + label: Browser and Browser Extension Version + description: Which browser (Chrome, Edge, Chromium, etc.) and BrowserSkill extension version (if applicable). + placeholder: e.g., Google Chrome 130.0.6723.70 / Extension 0.3.3 + validations: + required: true + - type: textarea + id: command + attributes: + label: Exact Command or API Call + description: The exact command, script invocation, or MCP/RPC tool call that triggered the problem. + placeholder: e.g., bsk click @e2 --session s1 + render: shell + validations: + required: true + - type: textarea + id: reproduction + attributes: + label: Minimal Reproduction Steps + description: Step-by-step instructions to reproduce the bug. + placeholder: | + 1. Start daemon with `bsk daemon start` + 2. Navigate to `https://example.com` + 3. Run `bsk observe --session s1` + 4. See error ... + validations: + required: true + - type: textarea + id: expected + attributes: + label: Expected Behavior + description: What did you expect to happen? + validations: + required: true + - type: textarea + id: actual + attributes: + label: Actual Behavior + description: What actually happened? + validations: + required: true + - type: textarea + id: logs + attributes: + label: Relevant Logs / Diagnostics Output + description: Output from `bsk logs`, `bsk doctor`, or stderr/stdout (ensure secrets and credentials are fully redacted). + render: shell + validations: + required: true + - type: dropdown + id: regression + attributes: + label: Is this a regression? + description: Did this behavior work in a previous version of BrowserSkill? + options: + - "No / Not sure" + - "Yes (please specify the last known working version below)" + validations: + required: true + - type: input + id: regression_version + attributes: + label: Last Known Working Version (if regression) + placeholder: e.g., 0.3.2 + validations: + required: false + - type: textarea + id: additional_context + attributes: + label: Additional Context + description: Any other context, screenshots, or configuration files (e.g. `daemon.json`, `~/.bsk/`). + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 00000000..3d78941a --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,8 @@ +blank_issues_enabled: false +contact_links: + - name: Security Vulnerability Reporting + url: https://github.com/Tencent/BrowserSkill/security/advisories/new + about: Please report security vulnerabilities privately. Do not open public issues for security vulnerabilities. + - name: GitHub Discussions & Questions + url: https://github.com/Tencent/BrowserSkill/discussions + about: Ask usage questions, share ideas, and connect with the community. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 00000000..23989480 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,67 @@ +name: Feature Request +description: Propose a new feature, enhancement, or improvement for BrowserSkill. +title: "[Feature]: " +labels: ["enhancement"] +body: + - type: markdown + attributes: + value: | + Thank you for suggesting an idea to improve BrowserSkill! + Please describe the problem you are trying to solve so we can understand the motivation behind your proposal. + - type: checkboxes + id: prerequisites + attributes: + label: Prerequisites + description: Please verify before submitting. + options: + - label: I have searched existing [open and closed issues](https://github.com/Tencent/BrowserSkill/issues) to confirm this feature hasn't already been requested. + required: true + - label: I understand that feature requests should focus on the underlying user need or problem rather than only an implementation detail. + required: true + - type: textarea + id: problem + attributes: + label: Problem or Use Case + description: What problem are you trying to solve? Who is affected? Why is the current behavior insufficient? + placeholder: Describe the user problem, workflow friction, or limitation you encountered. + validations: + required: true + - type: textarea + id: proposed_solution + attributes: + label: Proposed Behavior + description: How should BrowserSkill behave? Describe your desired solution. + placeholder: Explain the proposed behavior and how it addresses the use case. + validations: + required: true + - type: textarea + id: alternatives + attributes: + label: Alternatives Considered + description: What other approaches or workarounds did you consider, and why were they rejected? + placeholder: Alternative designs, scripts, or existing tools tried. + validations: + required: true + - type: textarea + id: affected_surface + attributes: + label: Affected CLI / API Surface + description: Which commands, flags, IPC protocol endpoints, or extension components would be affected? + placeholder: e.g., `bsk session`, `bsk daemon`, CDP bridge, extension popup, protocol schemas. + validations: + required: true + - type: textarea + id: compatibility + attributes: + label: Compatibility Considerations + description: Does this introduce breaking changes to the CLI interface, protocol schema, or platform requirements? + placeholder: Note any backward-compatibility impact or platform-specific considerations (Windows/macOS/Linux). + validations: + required: true + - type: textarea + id: additional_context + attributes: + label: Additional Context + description: Add any other context, mockups, or references here. + validations: + required: false From 87283aa4ca3d7169c39fd36c3af3405962e19757 Mon Sep 17 00:00:00 2001 From: legend91019 <15853153143@163.com> Date: Sun, 18 Oct 2026 23:37:20 +0800 Subject: [PATCH 2/4] feat(process): make logs and internal surface fields optional Address review feedback from issue #462: - Make relevant logs field in bug_report.yml optional to reduce friction when logs are unavailable. - Make affected CLI/API surface and compatibility considerations optional with N/A allowance in feature_request.yml. --- .github/ISSUE_TEMPLATE/bug_report.yml | 5 +++-- .github/ISSUE_TEMPLATE/feature_request.yml | 12 ++++++------ 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index d1765dc7..080663d7 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -111,10 +111,11 @@ body: id: logs attributes: label: Relevant Logs / Diagnostics Output - description: Output from `bsk logs`, `bsk doctor`, or stderr/stdout (ensure secrets and credentials are fully redacted). + description: Relevant output from `bsk logs`, `bsk doctor`, or stderr/stdout (optional, if available; ensure secrets and credentials are fully redacted). + placeholder: Paste any relevant logs, terminal output, or diagnostic info here (leave blank or enter "N/A" if not applicable). render: shell validations: - required: true + required: false - type: dropdown id: regression attributes: diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index 23989480..1246fe39 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -46,18 +46,18 @@ body: id: affected_surface attributes: label: Affected CLI / API Surface - description: Which commands, flags, IPC protocol endpoints, or extension components would be affected? - placeholder: e.g., `bsk session`, `bsk daemon`, CDP bridge, extension popup, protocol schemas. + description: Which commands, flags, IPC protocol endpoints, or extension components would be affected? (Optional / N/A if not sure). + placeholder: e.g., `bsk session`, `bsk daemon`, CDP bridge, extension popup, protocol schemas (leave blank or enter "N/A" if unknown). validations: - required: true + required: false - type: textarea id: compatibility attributes: label: Compatibility Considerations - description: Does this introduce breaking changes to the CLI interface, protocol schema, or platform requirements? - placeholder: Note any backward-compatibility impact or platform-specific considerations (Windows/macOS/Linux). + description: Does this introduce breaking changes to the CLI interface, protocol schema, or platform requirements? (Optional / N/A if not sure). + placeholder: Note any backward-compatibility impact or platform-specific considerations (Windows/macOS/Linux). Enter "N/A" if unknown. validations: - required: true + required: false - type: textarea id: additional_context attributes: From 5bdc892ec74a60a4aba00e73651ba5bc730ad1be Mon Sep 17 00:00:00 2001 From: legend91019 <15853153143@163.com> Date: Sat, 24 Oct 2026 08:40:57 +0800 Subject: [PATCH 3/4] fix(process): drop security/Discussions contact links and allow blank issues Per maintainer review: private vulnerability reporting and Discussions are disabled for this repository, so remove both contact links and the security-vulnerability checkbox (keeping duplicate-search and sensitive-data redaction checks), and set blank_issues_enabled: true so documentation and other issues still have a path. --- .github/ISSUE_TEMPLATE/bug_report.yml | 2 -- .github/ISSUE_TEMPLATE/config.yml | 9 +-------- 2 files changed, 1 insertion(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 080663d7..85431977 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -18,8 +18,6 @@ body: required: true - label: I have verified that all sensitive data (passwords, tokens, API keys, private URLs, personal info) have been redacted from logs and snippets. required: true - - label: This is a bug report and not a security vulnerability (see our [Security Advisories](https://github.com/Tencent/BrowserSkill/security/advisories/new)). - required: true - type: input id: version attributes: diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 3d78941a..0086358d 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,8 +1 @@ -blank_issues_enabled: false -contact_links: - - name: Security Vulnerability Reporting - url: https://github.com/Tencent/BrowserSkill/security/advisories/new - about: Please report security vulnerabilities privately. Do not open public issues for security vulnerabilities. - - name: GitHub Discussions & Questions - url: https://github.com/Tencent/BrowserSkill/discussions - about: Ask usage questions, share ideas, and connect with the community. +blank_issues_enabled: true From decbaa9a82c3dd08aab674be2d8207c5e663252b Mon Sep 17 00:00:00 2001 From: legend91019 <15853153143@163.com> Date: Sat, 24 Oct 2026 09:26:29 +0800 Subject: [PATCH 4/4] chore: retrigger CI (Browser video recording regression is flaky on main)