Lephenixnoir
/
GiteaPC
1
1
Fork 1
Code Issues 3 Pull Requests Releases Wiki Activity

git pull can fail when following a branch that gets force-pushed to #1

New Issue
Open
opened 2021-01-30 13:38:48 +01:00 by Lephenixnoir · 0 comments
Lephenixnoir commented 2021-01-30 13:38:48 +01:00
Owner
Copy Link

Maybe consider using git branch -f instead of git pull, assuming this works well with unindexed files.

Maybe consider using `git branch -f` instead of `git pull`, assuming this works well with unindexed files.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
1.1
1.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Lephenixnoir/GiteaPC#1
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?