How to Report Bugs or Request Features on GoKibitz

Updated

GoKibitz provides three separate feedback channels in its site footer: a Feature Requests link, a Bugs link, and a GitHub link. Use the Bugs link for something broken, Feature Requests for something you want added, and GitHub if you prefer to file or track issues in the code repository directly. All three are reachable from the footer on any page, and none of them require you to be logged in to find.

Which Channel to Use

What you have Where to send it
Something is broken or behaving incorrectly Bugs
An idea for a new capability or improvement Feature Requests
A preference for filing/tracking issues in the repo, or checking whether a bug is already known GitHub

The site itself does not describe a required format for either the Bugs or Feature Requests channel, so the practical rule is: pick the link that matches your intent and describe the problem or idea as concretely as you can.

What to Include in a Report

Since GoKibitz is built around move-by-move discussion of go games, the most useful reports point at a specific position or conversation rather than describing it in the abstract.

For a bug:

  • The page or game where it happened, with the URL if you have it
  • What you did (the action you took)
  • What you expected to happen
  • What actually happened
  • Whether it reproduces if you try again

For a feature request:

  • The task you were trying to accomplish
  • Why the current behavior made it hard or impossible
  • What a workable version of the feature would look like to you

A Note on the GitHub Link

The GitHub link points to the project's repository, which is the place to look if you want to see whether an issue has already been reported before adding a duplicate. The footer credits the project to Nate Eagle, and the GitHub entry sits alongside the Feature Requests and Bugs links as a third route into the same feedback process.

Common Snags

  • Reporting from the wrong channel. A crash filed under Feature Requests is easy to miss; a "please add X" filed under Bugs reads as a defect. Match the link to the intent.
  • Vague reports. "It doesn't work" gives nothing to act on. Naming the game, the move, or the page turns a complaint into something fixable.
  • Assuming you need an account. The footer links are visible on the public site; the Log In / Sign Up controls are separate from the feedback links.

If you are unsure whether something counts as a bug or a feature, file it under Bugs when the current behavior contradicts what the interface implies, and under Feature Requests when the current behavior is correct but incomplete.