Beta Version

Getting Started with VisualJJ

Jujutsu version control in Visual Studio Code

Welcome to VisualJJ! This guide will help you quickly start using VisualJJ in Visual Studio Code, harnessing the simplicity and power of Jujutsu for your version control needs. In just a few simple steps, you'll be making changes, sharing them for review, and shipping them to your main branch on GitHub.

Why VisualJJ?

VisualJJ is built on Jujutsu which simplifies many of the complex concepts found in traditional version control systems.

  • There’s no need to worry about staging or indexes — every change you make is automatically part of a commit.
  • Rebase operations are the norm, helping you maintain a clean and linear project history.
  • Conflicts can be resolved on your own time, without disrupting your workflow.
Features 03

Step 0: Clone or Open Your Repository

Before we begin, make sure you've either cloned a repository from GitHub using SSH or opened an existing repository in Visual Studio Code. VisualJJ works seamlessly with your existing projects.

If you don't have VisualJJ installed yet please click button below and follow instructions.

Install VisualJJ

Features 02

Step 1: Make a Change

In this step, you’ll make your first change by editing a file and describing what you’ve done. VisualJJ will automatically track your modifications as part of the current commit.

  • Navigate to the file you want to modify within your repository.
  • Make your desired changes and save the file.
  • In the VisualJJ tab, enter a brief description of your changes.
Features 03

Step 2: Share Your Change for Review

Now that you’ve made your change, you’ll create a branch, push your changes to GitHub, and share them for review by creating a Pull Request (PR).

  • Before pushing, create a new branch for your changes. This ensures your work is organized and follows GitHub’s workflow.
  • Click the "Push" button to send your changes to GitHub. VisualJJ will push your branch to the remote repository.
  • Open your browser, navigate to the GitHub repository, and create a Pull Request (PR) with your changes. "

Your change is now shared for review. If you need to modify your commits, simply make the changes and "Push" again in VisualJJ. The PR on GitHub will automatically update with your new commits.

Features 02

Step 3: Ship Your Change

Once your change is reviewed, it’s time to ship it to the main branch and clean up your workspace.

  • Once your PR is approved, merge it to the main branch on the GitHub website.
  • You can now delete the branch directly on GitHub using the "Delete Branch" button (or configure GitHub to delete it automatically upon merging).
  • Back in VSCode, use the "Fetch" command to update your local repository, which will remove the shipped commit and bring in the latest changes.

You're ready to start a new change from the updated main branch!

Explore More Features

Congratulations! You've successfully made, shared, and shipped your first change using VisualJJ. This is just the beginning—VisualJJ offers a range of powerful features designed to make version control easier and more efficient. For example, handling conflicting changes is much simpler and more intuitive compared to Git, allowing you to resolve conflicts at your convenience.

Need Help?

If you run into any issues or have questions, don’t hesitate to reach out to us at support@visualjj.com.