Working

Branches and pull requests

Work on its own branch

Tick "Work on its own branch" when you start a session, or use the branch button under the message box before the first message. Renviel makes a separate folder for a new branch, outside your project. Your own checkout and its uncommitted changes are left as they are.

You can choose the branch to start from and name the new one. Files git ignores but the project needs, such as .env, can be listed in a .worktreeinclude file at the top of the repository; they are copied into the new folder.

Settings → Data lists these folders and removes the ones no session uses. It can also archive a session once its pull request is merged or closed.

Commit, push and pull request

The Changes panel has a source control section for each repository the session works in: the branch, the uncommitted files, a commit box, Push and Pull request. An account can write the commit message or the pull request text for you; nothing is committed until you do it.

If a repository has git hooks or settings that run programs, Renviel shows them and asks before the first commit or push.

Checks and review comments

When the branch has a pull request on GitHub or a merge request on GitLab, the panel shows its checks. This needs the gh or glab command-line tool, signed in. "Send failing checks" puts the logs of the failed ones into your message, and "Send review comments" does the same with open review threads. You can merge from the same place.

Starting from an issue

Open a GitHub issue to put it into your message or to start a session on its own branch for it. Linear issues can be put into your message too.