Skip to content

Latest commit

 

History

History
34 lines (21 loc) · 1.91 KB

SUPPORT.md

File metadata and controls

34 lines (21 loc) · 1.91 KB

Where to get help

Bugs

If you think you've found a bug in any part of Creek, please first check the existing issues:

  • If you know the repository that hosts the code the bug is in, then please search the existing issues in that repository.

  • Otherwise, use and customise one of the following searches to search across all Creek repositories:

    NOTE the above searches can be customised with keywords, once opened, using the search box in the top left of the screen.

...if no one has reported the problem, please open a new issue:

  • If you know the repository that hosts the code the bug is in, then please open a new 'bug' issue in that repository.
  • Otherwise, create a Creek-wide bug report

Security vulnerability

If you think you've gound a vulnerability in any part of Creek, then please view our security policy.

Questions

If you have a question about Creek, then this is best handled using GitHub discussions. Please, first check the existing discussions:

  • If your question pertains to a specific component / repository, then please create a new discussion under that repository.
  • Otherwise, for more general questions, please create a Creek-wide discussion.

Timings

Creek is an open-source project maintained by volunteers. As such, we offer no hard and fast guarantees on response times. However, we aim to respond to all questions and issues within 7 days.