Ryker / Docs / Your first code change

Your first code change

Ask Ryker to fix a small bug, follow the work in Slack, and review the result in GitHub. Use a change with a clear expected result so you can judge the code and its tests.

Choose the repository

You need Ryker installed, a connected GitHub repository, and a Slack channel it has joined. In the channel’s environment, give the target repository read/write access. Keep related repositories read-only if they are needed for context.

An active full Slack member can start the task. An operator will need to enable draft pull requests under Integrations › GitHub if they have not already done so.

Ask for a specific change

Replace the repository and behavior with a bug in your project:

@Ryker in your-team/your-repository, reject an empty email address when creating a user. Return the same validation error as other invalid inputs. Add a regression test and run the relevant tests.

Read the proposed task, then press Start task. Ryker creates a separate working copy and begins. If it only explains the change, ask it to prepare the edit as a task.

Follow the work in the thread

The task card updates as Ryker plans the change, edits the code, and runs checks. Answer any questions in that thread. Further replies there continue the task without another mention.

Ryker reviews the change against the current repository and runs your configured checks before publishing. A failed check or rebase conflict stops publication. A check that did not run is recorded as missing.

If work stops, read the question or failure. A missing dependency needs a different response from a failed test. The request’s timeline has the commands and results; installation problems are covered under troubleshooting.

Open the draft pull request

After review, Ryker can open the draft for the repository included in your confirmed task. If it needs separate publication approval, an operator presses Create draft PR. Draft publication must be enabled for either path. The task card then offers Open PR.

The draft contains the reviewed change on a Ryker-owned branch. Missing or unavailable checks can produce a draft marked unverified. Read the diff and the actual test results in GitHub. For the example above, check that empty input produces the expected error and valid input still works.

Ask for changes and finish the review

Leave feedback on the pull request or in the original Slack thread. For example:

Also handle an email address containing only spaces. Add a test for that case and keep the error response consistent.

Review comments return to the same task. Failed CI on Ryker’s published commit can also resume the task so it fixes the failure within its scope and updates the same pull request. You do not need to ask it to repair each failed check.

When you are satisfied with the change and checks, your team marks the draft ready, merges it, and releases it. Ryker reports the pull request’s outcome in the original thread.