When provider bad-formatted config files, the error output may be confusing. In the example below, the config file is a empty file, and the output will cause people trying to debug their network connections.
Linked issue: https://github.com/go-gitea/gitea/pull/25256
When provider bad-formatted config files, the error output may be confusing. In the example below, the config file is a empty file, and the output will cause people trying to debug their network connections.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Linked issue: https://github.com/go-gitea/gitea/pull/25256
When provider bad-formatted config files, the error output may be confusing. In the example below, the config file is a empty file, and the output will cause people trying to debug their network connections.
I think just have a
Failed to parse config fileoutput would resolve this issue. I could make a pr to address that.