Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve the workdir status handling #374

Open
draftcode opened this issue Aug 1, 2024 · 0 comments
Open

Improve the workdir status handling #374

draftcode opened this issue Aug 1, 2024 · 0 comments

Comments

@draftcode
Copy link
Contributor

If a command internally start git rebase or git switch, we should make sure that the workdir is clean.

In order to check the status more comprehensively, we can use git status --porcelain=v2.
@draftcode draftcode mentioned this issue Aug 7, 2024
Merged
aviator-app bot pushed a commit that referenced this issue Aug 7, 2024
@draftcode
Use git-status to get the status of the repository (#385)(#384)
0d3ef28 
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


Detect the branch structure in a more robust way
This should address the issue where the stack adopt command fails when
it's invoked at the trunk branch. (#363)

Based on the feedbacks, it seems that the commit traversal is way slower
than expected. Try to be a bit more conservative when to traverse the
commits.


Closes #384
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@draftcode