Make a repository change and open a pull request

Use a hosted workspace to inspect a GitHub repository, make a focused change, check it, and open a pull request. You need a hosted plan, a GitHub account with permission to work on the repository, and available model usage.

This workflow uses the Developer workspace. Free Browser projects do not clone repositories or open pull requests.

1. Connect GitHub

Open Settings, find GitHub, and choose Connect GitHub. Complete GitHub's authorization screen, then return to Rigless. The GitHub section should show the connected account.

The ordinary repository connection uses GitHub authorization. Automated GitHub event workflows have separate setup; you do not need to configure those to follow this guide.

2. Choose the repository and agent

Open Developer workspace. Use Choose a repo to select your repository, then choose the branch you want to start from. Select a hosted agent and a compatible model using the controls above and below the task field. The default hosted agent and included model are enough to begin.

Pick a small task you can review. A first change should have a clear expected behavior and a way to check it. Replace the bracketed part of this request with your task:

Inspect this repository and its development instructions first.
My task is: [describe one small bug or change and the expected result].
Explain which files you need to change, then implement the fix on a work branch.
Run the relevant checks and tell me the exact commands and their results.
Preserve unrelated work. Leave pushing and opening the pull request to me.

Select the upward-arrow Start task button. Rigless creates the session and prepares the hosted workspace. If cloning fails, resolve that error before asking the agent to proceed.

3. Review the implementation

Read the agent's result, including any check it could not complete. Open the three-dot Session menu and choose Changes to inspect the diff. The same menu gives you Files and Terminal when you want to examine the implementation or run a command yourself.

Confirm the changed files match your task and that the reported checks cover the behavior you care about. For an application change, open its preview and try the behavior yourself.

If something needs adjustment, ask for it in the same conversation before creating the pull request.

4. Open the pull request

In Changes, choose Create PR. Review the title and description, then choose Create pull request. This action sends the work to GitHub, so inspect the diff first.

Open the resulting PR link on GitHub. Confirm the target repository and branch, inspect the final diff, and check any repository CI results. Opening a pull request leaves review and merging in your normal GitHub workflow.

If you get stuck

Problem	Check
The repository controls are missing	Open Developer workspace and confirm your plan supports hosted compute
Your repository is absent	Check the connected GitHub account and its permission to access that repository; organization authorization may also be required
Cloning or pushing fails	Read the error, check access and branch protection, and reconnect GitHub if authorization has changed
Create PR is missing	Confirm the session is connected to a repository, contains changes, and does not already have a linked pull request
The agent could not run a check	Inspect the command output and missing setup; resolve it before treating the change as verified
GitHub reports conflicting changes	Update the branch and resolve the conflict before merging

To share a running application as well as its source change, continue with Publish an app.