jingchen2222 / git-rs

git rust version

Hi there 👋

• 🔭 I’m currently working on DB3
• 🌱 I’m currently learning Rust

git-rs's Issues

support git status showing modified but not staged files

When you open an issue for a feature request, please add as much detail as possible:

• A descriptive title
• A description of the problem you're trying to solve, including why you think this is a problem
• An overview of the suggested solution
• If the feature changes current behavior, reasons why your solution is better

See here for more detail on what is expected of a feature request.

Description

A file in the working directory is “modified but not staged” if it is

• Tracked in the current commit, changed in the working directory, but not staged; or
• Staged for addition, but with different contents than in the working directory; or
• Staged for addition, but deleted in the working directory; or
• Not staged for removal, but tracked in the current commit and deleted from the working directory.

support git branch cmd

Before you open an issue, please check if a similar issue already exists or has been closed before.

When you open an issue for a feature request, please add as much detail as possible:

• A descriptive title
• A description of the problem you're trying to solve, including why you think this is a problem
• An overview of the suggested solution
• If the feature changes current behavior, reasons why your solution is better

See here for more detail on what is expected of a feature request.

Description

Add git branch cmd

display untracked file for `git status`

When you open an issue for a feature request, please add as much detail as possible:

• A descriptive title
• A description of the problem you're trying to solve, including why you think this is a problem
• An overview of the suggested solution
• If the feature changes current behavior, reasons why your solution is better

See here for more detail on what is expected of a feature request.

Description

The final category (“Untracked Files”) is for files present in the working directory but neither staged for addition nor tracked. This includes files that have been staged for removal, but then re-created without git-rs knowledge.

support git checkout file and branch

When you open an issue for a feature request, please add as much detail as possible:

• A descriptive title
• A description of the problem you're trying to solve, including why you think this is a problem
• An overview of the suggested solution
• If the feature changes current behavior, reasons why your solution is better

See here for more detail on what is expected of a feature request.

Descriptions:

Checkout file

Takes the version of the file as it exists in the head commit and puts it in the working directory, overwriting the version of the file that’s already there if there is one. The new version of the file is not staged.

Checkout commit_id file

Takes the version of the file as it exists in the commit with the given id, and puts it in the working directory, overwriting the version of the file that’s already there if there is one. The new version of the file is not staged.

Checkout branch

Takes all files in the commit at the head of the given branch, and puts them in the working directory, overwriting the versions of the files that are already there if they exist. Also, at the end of this command, the given branch will now be considered the current branch (HEAD). Any files that are tracked in the current branch but are not present in the checked-out branch are deleted. The staging area is cleared, unless the checked-out branch is the current branch (see Failure cases below).