Skip to content

Latest commit

 

History

History
41 lines (30 loc) · 1.72 KB

SUPPORT.md

File metadata and controls

41 lines (30 loc) · 1.72 KB

Support

Current support level

wip-commit is beta software. Support is best effort, and there is no response-time or resolution-time guarantee. A local candidate and a published prerelease have the same beta support boundary.

The newest published beta is the only supported beta unless a release note says otherwise. A published stable version will define a separate support policy.

Ask for help

After the repository is public, use its issue tracker for reproducible bugs and its discussion area for usage questions, if discussions are enabled. Do not put secrets, private paths, repository names, file contents, commit messages, or credentials in a report.

For a security issue, follow SECURITY.md. Do not report a suspected vulnerability in a public issue.

Community participation follows CODE_OF_CONDUCT.md. Use the repository host's private reporting form on the Security tab for a confidential conduct report. Start the title with Code of Conduct:. Do not put a conduct report in a public issue.

Report a capture problem

If you suspect that a command captured foreign content or changed the wrong ref:

  1. Stop further capture and landing work.
  2. Preserve the worktree, index, agent ref, JSON result, and recovery receipt.
  3. Run wip doctor and record only redacted output.
  4. Do not stash, reset, clean, force-update, or delete state.
  5. Report the wip version, operating system, Git version, command outcome, typed error code, ref_updated, and intent_state.

The project does not promise recovery from manual changes to its state files, uncoordinated Git index mutation, malicious same-user processes, or commands outside the trust boundary in THREAT-MODEL.md.