Use git-status to get the status of the repository

[draftcode]

This conveniently provides the status of the repository in a structured
way. This can be used to get the current branch name (or detached
state), the OID, and all staged, unstaged, unmerged, untracked files.

Related to #374

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged using Aviator.

Stack

1. 👉 Use git-status to get the status of the repository #385 👈 (this pr)

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[aviator-app]

FlexReview Summary

Based on the code complexity and the author's expertise score, these are the suggested reviewers:

• @jainankit (current review load: 2)

See the list of alternate reviewers in the detailed breakdown below.

Detailed Breakdown

Author’s expertise score for the modified files:

• cmd/av/commit_split.go (1.00)
• cmd/av/stack_adopt.go (1.00)
• cmd/av/stack_restack.go (1.00)
• cmd/av/stack_switch.go (1.00)
• cmd/av/stack_sync.go (1.00)
• cmd/av/stack_tree.go (1.00)
• internal/git/git.go (1.00)
• internal/git/status.go (1.00)

Files	Reviewers
cmd/av/commit_split.go †, cmd/av/stack_adopt.go †, cmd/av/stack_restack.go †, cmd/av/stack_switch.go †, cmd/av/stack_sync.go †, cmd/av/stack_tree.go †, internal/git/git.go †, internal/git/status.go †	@jainankit (score: 0.65, current review load: 2)

† Indicates that the file doesn't need an expert review. (?)

See full breakdown of the reviewers on the Aviator webapp.

[aviator-app]

This pull request failed to merge: merge conflict detected, please resolve manually and requeue. Once the issues are resolved, remove the blocked label and re-queue the pull request. Note that the pull request will be automatically re-queued if it has the mergequeue label.

Additional debug info: Failed to merge changes from the base branch into this PR. You will probably need to merge the latest changes from the base branch into the PR branch and manually resolve conflicts.