All ok, but why this has to be storage model based on s3? There are many more suited object storage models out there.
For instance, say my repo has Issue templates, one for problems (basically support/find my bug) and one for bugs where the problem and solution are documented.
@billynoah if you ask me than yes, this issue is sufficient, but I have no power to reopen it. Im not a maintainer.
@TheBrambleShark you mean something like GitHub's this issue relates to issue Y', or merging PR will close related issue'?
which is not a reasonable expectation for users.
the fork count and the forks list are out of sync
@billynoah For most Linux distros, the default cache folder is in /var/cache. Clean this.
@billynoah thats not doable from within Forgejo's own webUI. You need to log in as root via ssh and manually delete everything from within cache folder. **Beware not to delete folder...
@billynoah From what you have provided, my wild guess would be start from purging and rebuilding cache.
CommitUser.Date is the only date field in the API structs treated as string
@harabat While I can clearly see what you suggesting, I fail to see/produce any justification for it to be implemented.
Basically two questions here:
@mfenniak These are the exact steps I took :)
On a funny side:
@earl-warren That was blazing fast. Thank you
Just to inform you @forgejo-moderation that link to CoC above is not working (404 error)
@earl-warren if OVH says that domain expires in 2033 than there is absolutely no need to check it yearly till, say, 2032.....
@fnetX noticed this also, but thought that this is on purpose. Never thought its a bug. Why this matters to you?