Report an issue

Use GitHub Issues for product defects and documentation problems. Use a private GitHub Security Advisory for vulnerabilities; never put exploit details or secrets in a public issue.

What you need

• A GitHub account that can open an issue or security advisory.
• The smallest reproducible sequence and current Oore versions.
• Redacted logs, identifiers, or screenshots only when they help reproduce the problem.

1. Capture the environment

Record:

• macOS version and hardware architecture;
• Oore release channel and setup path;
• Local Only or the exact External Access subtype;
• installed, self-hosted, or hosted browser client; and
• source provider and target build platform when relevant.

Capture command versions and diagnostics:

oore version
oored version
oore status --json
oore doctor --json

2. Write one reproduction

Include:

1. The single job you were trying to complete.
2. Numbered clicks or commands starting from a known state.
3. The expected observable result.
4. The actual result, including exact status and machine-readable error code.
5. The smallest relevant log excerpt, build ID, or screenshot.

For a documentation issue, include the exact page URL and the statement or step that is unclear or wrong.

3. Redact before attaching

Remove session, setup, runner, upload, download, signing, and provider tokens; cookies; client secrets; private keys; credentials; and sensitive source or host information. Keep timestamps, command names, status codes, and enough neighboring log context to establish order.

4. File in the right place

• Open a public Oore issue and choose Alpha Test Report, Bug Report, or Docs Feedback.
• Open a private security advisory for a vulnerability.

Verify the result

Read the issue after submission. Confirm another person can identify the goal, environment, exact steps, expected result, actual result, and evidence without asking for a secret.

Troubleshooting

If you cannot attach a log safely, replace sensitive values consistently and paste only the smallest relevant section. If GitHub Security Advisories are unavailable, open a minimal public issue asking for a private contact channel without disclosure details.

Next step

Keep the affected instance and original evidence unchanged until triage confirms what else is needed.