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.

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

Feature: Use get reset --hard instead of git pull for updating repo #98

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

zeerayne
Copy link
Contributor

This feature is useful, when user is on non-main HyDE branch, and this branch was force-pushed in remote repo (for example, rebased on main branch).

In current scheme with git pull attempt to update on force-pushed branch will fail, but if use get reset, branch will be updated successfully.

In other cases it behaves exact as git pull.

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Nov 27, 2024

Lemme know in case there's a problem.Will merge it now

@kRHYME7 kRHYME7 merged commit e5d5a6a into HyDE-Project:master Nov 27, 2024
1 check passed
@zeerayne
Copy link
Contributor Author

Have updated hyde-cli-git from AUR, then update repo with Hyde update, all seems working as expected

image

@zeerayne zeerayne deleted the feature-reset-instead-pull branch November 27, 2024 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants