Pushing commits to exogit results in warning #153

New issue

Closed

opened 2022-06-11 23:24:49 +00:00 by a · 1 comment

a commented

2022-06-11 23:24:49 +00:00

Owner

Here's an example:

git push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 985 bytes | 985.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: 2022/06/11 18:23:45 modules/git/git.go:138:HomeDir() [E] [62a52401-4] Git's HomeDir is empty (RepoRootPath is empty), the git module is not initialized correctly, using a temp HomeDir (/tmp/gitea-temp-home) temporarily
remote: . Processing 1 references
remote: Processed 1 references in total
To git.exozy.me:Ta180m/dotfiles.git
   904e81b..383c278  main -> main

Here's an example: ``` git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 8 threads Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 985 bytes | 985.00 KiB/s, done. Total 3 (delta 1), reused 0 (delta 0), pack-reused 0 remote: 2022/06/11 18:23:45 modules/git/git.go:138:HomeDir() [E] [62a52401-4] Git's HomeDir is empty (RepoRootPath is empty), the git module is not initialized correctly, using a temp HomeDir (/tmp/gitea-temp-home) temporarily remote: . Processing 1 references remote: Processed 1 references in total To git.exozy.me:Ta180m/dotfiles.git 904e81b..383c278 main -> main ```

a added the

bug

label 2022-06-11 23:24:49 +00:00

a self-assigned this 2022-06-11 23:24:49 +00:00

a added this to the (deleted) project 2022-06-11 23:24:49 +00:00

a started working 2022-06-11 23:24:51 +00:00

a commented

2022-06-11 23:46:55 +00:00

Author

Owner

This is fixed by 1a8955dc4f to my Gitea ActivityPub fork. I'm not too sure why this bug is appearing in the first place since we obviously have a nonempty RepoRootPath as the other logs confirm, but maybe it's just a sympton of using bleeding edge Gitea.

This is fixed by [1a8955dc4f](https://gitea.com/Ta180m/gitea/commit/1a8955dc4febb5cd63aec45f53d9c72bb4895848) to my Gitea ActivityPub fork. I'm not too sure why this bug is appearing in the first place since we obviously have a nonempty `RepoRootPath` as the other logs confirm, but maybe it's just a sympton of using bleeding edge Gitea.

a closed this issue

2022-06-11 23:46:55 +00:00

a stopped working 2022-06-11 23:46:55 +00:00

22 minutes 4 seconds