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
The file is gone since #30055, but as it is not in .gitignore any more, it will show up if you build the 1.22 branch, switch to main and execute git add --all.
Either delete it manually or we re-add public/assets/img/webpack to gitignore.
Fixes#30442
It's inconvenient to have new untracked files show up in git when
switching to older branches that had generated them.
Introduce a list of such files and folders to gitignore and
dockerignore.
Fixesgo-gitea/gitea#30442
It's inconvenient to have new untracked files show up in git when
switching to older branches that had generated them.
Introduce a list of such files and folders to gitignore and
dockerignore.
(cherry picked from commit 68271834d6ae6d397b5a2048f9e515ff53735994)
go-gitea
locked as resolved and limited conversation to collaborators
Jul 12, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
type/questionIssue needs no code to be fixed, only a description on how to fix it yourself.
Feature Description
After update the branch, I got this new file, is this an issue? or just ignore it?

Screenshots
No response
The text was updated successfully, but these errors were encountered: