-
Notifications
You must be signed in to change notification settings - Fork 48
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
error in process sentinel: fatal: invalid object name 'fatal' #151
Comments
Thanks, I'll fix this soon. |
@bcc32 That seems to fix it. Please let me know if it does for you. |
Unfortunately I'm getting the same error. In the repo where I'm getting the error, I evaluated:
which returned:
This is a repo whose default branch is called I tried in a repo whose default branch is still called Should magit-todos perhaps automatically determine the default branch name by asking git? ( |
What happens if you set the option |
It works fine when that variable is set to |
I still encountered this issue with |
I'm also seeing this on 20230819.732, though the workaround in #151 (comment) does work for repos where the main branch is 'main' or 'master'. |
Fixes #151. Closes #152. Reported-by: Aaron Zeng <https://github.com/bcc32>
The new update seems to work correctly for me, without customizing |
Thanks, Aaron. |
After the recent update, I see the following error messages appear after magit-todos runs (before its output is inserted into the magit-status buffer):
The text was updated successfully, but these errors were encountered: