Reference · the tools
send_feedback
What it does
Tell the Bettik team about Bettik itself: a tool that failed or said something wrong, a step that was confusing or took too many calls, something missing. Send it when the user asks. When Bettik got in your way, offer to send it, in a line, and send it if they agree. Write what you were doing, what you called, what came back and what you expected: you saw it, and a person rarely writes it down. Not for the code or app inside a bundle, which is its author's. Small text, such as a log or an error, can go in attachments. Screenshots and other files cannot go in the call. It returns a link for them: curl -F file=@<path> from a shell, or open it in a browser.
What it needs to know
- message
- What happened and what you expected; for an idea, what it would let you do. Plain words, as much as it takes.
- kind · optional
- bug: something broke or was wrong. confusing: it worked, but a description or an answer misled you. idea: something Bettik could do. Default other. One of
bug,confusing,idea,other. - tool · optional
- The Bettik tool it is about, if any: "install_environment".
- bundle · optional
- The bundle it is about, if any.
- box · optional
- The box it is about, if any: "home.frank".
- error · optional
- The error as it came back, word for word.
- attachments · optional
- Text to keep with the report as files: a log, a transcript excerpt, a config. Not images: use the link the report returns.
- session_box · optional
- The box this session runs on, if it runs on one of yours: its name, as the on-box instructions give it ("frankh90.hemlane"). With it, a call that names no box is checked against your current box.
Where it lands
On one of your boxes: the one named in box, or your default box when none is named.