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
[skip ci] Updated translations via Crowdin (+7 squashed commit)
Squashed commit:
[e1468e2] Fixes for unreachable project issues when transfer repository from organization (go-gitea#31770)
dfhgfdhfghfg
When transferring repositories that have issues linked to a project
board to another organization, the issues remain associated with the
original project board. This causes the columns in the project board to
become bugged, making it difficult to move other issues in or out of the
affected columns. As a solution, I removed the issue relations since the
other organization does not have this project table.
Fix for go-gitea#31538
Co-authored-by: Jason Song <[email protected]>
[c39643f] fghfghf
[38a09ea] render plain text file if the LFS object doesn't exist (go-gitea#31812)gfgdfg
We had an issue where a repo was using LFS to store a file, but the user
did not push the file. When trying to view the file, Gitea returned a
500 HTTP status code referencing `ErrLFSObjectNotExist`. It appears the
intent was the render this file as plain text, but the conditional was
flipped. I've also added a test to verify that the file is rendered as
plain text.
[2477511] Add spacing to global error message (go-gitea#31826)
Fixesgo-gitea#31717.
Include Typescript files in Tailwind config so they can be
pre-processed.

[5bcab0b] [skip ci] Updated translations via Crowdin
[fe7c941] Scroll images in project issues separately from the remaining issue (go-gitea#31683)
As discussed in go-gitea#31667 & go-gitea#26561, when a card on a Project contains
images, they can overflow the card on its containing column. This aims
to fix this issue via snapping scrollbars.
---
Issue go-gitea#31667 is open to discussion as there should be room for
improvement.
[8883d99] Support issue template assignees (go-gitea#31083)
Resolvego-gitea#13955
// if there is no BranchPath, then the link will be something like "/owner/repo/src/{the-file-path}"
26
20
// and then this link will be handled by the "legacy-ref" code and be redirected to the default branch like "/owner/repo/src/branch/main/{the-file-path}"
0 commit comments