You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, it's Ann! I'm having problems keeping new emails now. Please
Note, I am prioritizing time the best I can on a phone. Thanks beyond words for the help.
To help us keep things tidy and focus on the active tasks, we've introduced a stale bot to spot issues/PRs that haven't had any activity in a while.
This particular issue hasn't had any updates or activity in the past 90 days, so it's been labeled as 'stale'. If it remains inactive for the next 30 days, it'll be automatically closed.
We understand everyone's busy, but if this issue is still important to you, please feel free to add a comment or make an update to keep it active.
pjbgf
added
bug
Something isn't working
help wanted
Extra attention is needed
and removed
stale
Issues/PRs that are marked for closure due to inactivity
labels
Dec 14, 2023
Found that out after running
git fsck
on a repo where I've been using go-git (through git-bug):Turns out that tree entries need to be sorted when serialized. Beware thought, it's a slightly peculiar order: isomorphic-git/isomorphic-git#937
I would assume that it would be go-git's reponsibility to ensure valid stored data.
The text was updated successfully, but these errors were encountered: