How to use DuckyHelper in Bitbucket
Reviews and failing pipelines wait on someone reading carefully. Ask DuckyHelper about the diff or the log on screen and it explains it and circles the line that matters. Hand it the reviewers, the comment or a new branch, and it does it in Bitbucket and is built to ask before posting (Early access).
See what a pull request changes
“What changed in this pull request, in plain words?”
- 01Open the pull request's diff so the changed lines are on screen, then ask out loud.
- 02DuckyHelper reads what was removed and what was added.
- 03It says what the change does in plain words and circles the function that changed.
- 04Ask who else calls that function and it tells you what the diff itself shows, and what to check.
You getA summary you can repeat in one sentence, and the function to read first.
Invoice totals are now rounded to two decimals before they are saved. The rest of the file is unchanged.
Read a failing pipeline step
“Why does this pipeline step fail?”
- 01Open the failed pipeline step so its log is on the screen, then ask out loud.
- 02DuckyHelper reads the commands and the output down to the last line.
- 03It circles the error and underlines the test that hit it, then says what is missing.
- 04Ask what to do next and it gives the one change to try first.
You getYou know what the step needs, in the log's own words, and where to look.
The test cannot find the tax module. Either the file is missing from the branch or the import path is wrong.
Add reviewers and say it's ready
“Add Ben and Ana as reviewers and comment that it's ready”
- 01Open the pull request, or say its title.
- 02DuckyHelper finds the Reviewers field and adds Ben and Ana with its own cursor.
- 03It writes a short comment saying the pull request is ready for review.
- 04It stops before posting and shows the comment. Press Send, Edit it, or Deny.
Built to ask firstAdding reviewers needs no OK from DuckyHelper, but the comment shows with Send, Edit and Deny first. Nothing is posted until you press Send.
You getThe right two people are on the pull request, and the comment goes out after you read it.
Start a branch for a ticket
“Create a branch for PAY-212 from main”
- 01Open the repository in Bitbucket, or say its name.
- 02DuckyHelper opens the screen for a new branch and picks main as the starting point.
- 03It types a branch name with the ticket key, PAY-212, in front.
- 04It creates the branch and tells you its name, and shows you the new branch on screen.
Built to ask firstCreating a branch needs no OK. It never merges or pushes, and a step that posts something is built to stop for you first.
You getA branch named for the ticket, created from main, ready for the first commit.
Getting more out of it in Bitbucket.
- 01
Open the Diff view, not the overview, before you ask what changed. It reads the lines on the screen.
- 02
Say the ticket key out loud, like PAY-212, and it uses it in the branch name.
- 03
For a pipeline, scroll to the first error. Later lines are usually the fallout.
- 04
It never merges or pushes. Pressing Merge stays yours.
Questions about Bitbucket.
Do I need to connect my Bitbucket account?
No. There is nothing to connect. It sees what is on your screen while the pill is open, and for jobs (Early access) it uses Bitbucket in your browser, signed in as you. It's built not to type your passwords or card numbers.
Can it merge a pull request?
No. It never merges or pushes on its own. A comment or anything else that posts is built to stop with Send, Edit and Deny first.
Does it read all my repositories?
No. Only what is on your screen while the pill is open. A job you start (Early access) opens the pages that job needs.
Does it work in the Bitbucket mobile app?
No. DuckyHelper is an app for Mac, Windows and Linux, so it works with Bitbucket in your computer's browser.
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.