From ae22379668b34cde6f0ce8e5ad0bc5ec98934852 Mon Sep 17 00:00:00 2001 From: amankumarsingh77 Date: Sat, 2 May 2026 00:08:22 +0530 Subject: chore: prepare v0.1.0 release - Add hero image for pi package gallery - Update CHANGELOG with release date - Update README with npm install instructions - Add assets/ to npm package files - Add CONTRIBUTING.md and GitHub templates - Add CI workflow for typecheck and pack validation --- .github/ISSUE_TEMPLATE/bug_report.md | 40 ++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md (limited to '.github/ISSUE_TEMPLATE/bug_report.md') diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..87023dc --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,40 @@ +--- +name: Bug report +about: Report a reproducible problem with pi-browser-harness +title: "[Bug]: " +labels: bug +assignees: "" +--- + +## Description + +Describe the problem clearly. Include what browser action or pi tool failed, if applicable. + +## Steps to Reproduce + +1. +2. +3. + +Please include the exact prompt, command, or tool call sequence when possible. + +## Expected Behavior + +What did you expect to happen? + +## Actual Behavior + +What happened instead? Include error messages, screenshots, or relevant logs if available. + +## Environment + +- OS: +- Node version (`node --version`): +- Chrome / Chromium / Edge version: +- pi version: +- pi-browser-harness version or commit: +- Install method (`npm`, `git`, local path): + +## Additional Context + +Add any other context that may help diagnose the issue, such as whether Chrome remote debugging was enabled through `chrome://inspect/#remote-debugging` or launched with `--remote-debugging-port=9222`. -- cgit v1.2.3