Skip to content

Commit f88e305

Browse files
committed
docs: add support guide
1 parent 3b10b60 commit f88e305

1 file changed

Lines changed: 53 additions & 0 deletions

File tree

SUPPORT.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Support
2+
3+
BrowserTrace is early open-source software. The best support path depends on
4+
what you need.
5+
6+
## Questions and Launch Feedback
7+
8+
Use the launch discussion:
9+
10+
https://github.com/aaronlab/browsertrace/discussions/6
11+
12+
Good topics:
13+
14+
- Which browser-agent stack you use.
15+
- What failed run was painful to debug.
16+
- What trace data you wish BrowserTrace captured.
17+
- Whether portable HTML exports are enough for your team.
18+
19+
## Bugs
20+
21+
Open a bug report:
22+
23+
https://github.com/aaronlab/browsertrace/issues/new?template=bug_report.yml
24+
25+
Please include:
26+
27+
- BrowserTrace version.
28+
- Python version.
29+
- Agent/browser stack.
30+
- Reproduction steps.
31+
- Exported trace or `browsertrace show <id>` output if it is safe to share.
32+
33+
## Feature and Integration Requests
34+
35+
Open a feature request:
36+
37+
https://github.com/aaronlab/browsertrace/issues/new?template=feature_request.yml
38+
39+
Open an integration request:
40+
41+
https://github.com/aaronlab/browsertrace/issues/new?template=integration_request.yml
42+
43+
Current roadmap:
44+
45+
https://github.com/aaronlab/browsertrace/milestone/1
46+
47+
## Security
48+
49+
Do not post secrets, private screenshots, customer data, cookies, tokens, or
50+
private prompts in public issues.
51+
52+
See `SECURITY.md` for security reporting guidance.
53+

0 commit comments

Comments
 (0)