Skip to main content

Collaborate with Git and Qixin Code

When to use this guide​

Use the Git panel when several people maintain one app, when changes require an audit trail, when you need a known version, or when the project must be backed up to a remote repository.

Before you start​

  • Git is available from the Git icon in the desktop editor's left Activity Bar.
  • Agree on the main branch, feature-branch naming, and merge owner before editing.
  • To use Qixin Code, sign in to Qixin and make sure the account has a name.
  • Save open Pages and Graphs before Pull, branch switches, or history checkout.

Steps​

Establish a repository and remote​

For a new app, you can enable Qixin Code during creation. For an existing app:

  1. Open the Git panel.
  2. If it is not a repository, select Enable Qixin Code or Initialize repository.
  3. For an existing Git repository, open the remote selector:
    • Select Switch to Qixin Code to create and connect a private repository; or
    • Select Add remote and enter a remote name and URL.
  4. Confirm that the selected remote is origin or the remote agreed by the team.
  1. Verify the current branch in the branch menu. For independent work, select Create and checkout new branch.
  2. Select Fetch to update remote branch information, then Pull the current branch.
  3. Complete and test one small, related set of changes.
  4. Under Changes, select each file and inspect its diff.
  5. Stage only the files for this task. Leave unrelated files unstaged.
  6. Enter a clear message and Commit. After staging changes, AI can propose a message, but review it before committing.
  7. Push the current branch.
  8. Follow the team's review and merge process. After merge, other contributors Pull again.

Inspect an older version​

  1. Open History and Fetch first if remote references need updating.
  2. Inspect the commit subject, author, time, and branch labels.
  3. Double-click a commit only to inspect that version. A history checkout enters detached HEAD; create a branch from that commit before continuing development.

What success looks like​

  • The Git panel shows the expected current branch and remote.
  • A commit contains only task files, with no secrets, site data, or generated files in its diff.
  • After Push, the same commit appears in the remote repository.
  • A teammate can Pull, open the app, and obtain the same editable project.

Common issues​

There are uncommitted changes before Pull​

Commit the work, or explicitly decide which changes to keep, stash, or discard. Do not switch commits or branches until you understand the effect of each option.

Push or Pull requests authentication​

For an HTTPS remote, update the access token through the prompt and retry. For SSH, check the local SSH key and agent. Never put credentials in the remote URL.

Qixin Code is unavailable​

Confirm that you are signed in to Qixin, the account has a name, and the account is allowed to use code management.

The same file has a conflict​

Stop editing and agree with the teammate on the business intent of both sides. Resolve each conflict and rerun the relevant tests. Do not replace the entire file with only one side without reviewing it.

I want to discard a file under Changes​

Discard restores a tracked file and deletes an untracked file. Use it only after confirming that the local work is no longer needed.

How AI can help​

AI can review changes, suggest commit boundaries, explain conflicts, and draft commit messages. For example:

Review the current Git changes without modifying them. Suggest the smallest independent commits by business purpose, identify files that should not be committed, and draft one message per commit. Do not stage, commit, or push.

After AI modifies an app, ask for the changed-file list and validation results. Still inspect every diff in the Git panel.

What a person must confirm​

  • The current branch, remote, and destination repository are correct.
  • Staged files belong only to this task and contain no secrets, customer data, or machine-specific settings.
  • The effect of Pull, branch switching, Discard, stash, and detached HEAD on uncommitted work.
  • The correct time to Commit and Push, and whether team review is complete.