Re-commit LFS files to fix broken stale (unstaged) files. @celenity, please check the images, maybe it will cause the build to fail or... not.
fix: re-commit .zip and .png files #262
koru/Phoenix:lfs into dev @ivankopylov6603 I think it's a good idea to commit these as LFS files - but do you think there's a way we can still view/download the files directly from Codeberg? Here's an example of what I envision this looking like from the IronFox F-droid repo - we upload the .apk files there as LFS, but it's still possible to view/download them directly from the web - that doesn't seem to be the case with these files here for whatever reason.
@celenity wrote in #262 (comment):
@ivankopylov6603 I think it's a good idea to commit these as LFS files - but do you think there's a way we can still view/download the files directly from Codeberg? Here's an example of what I envision this looking like from the IronFox F-droid repo - we upload the
.apkfiles there as LFS, but it's still possible to view/download them directly from the web - that doesn't seem to be the case with these files here for whatever reason.
I think I didn't commit correctly, it looks like they're broken. I'll figure out what happened.
And yes, here is an example of a working file.
2102ac3bc5
to 294010a284
I tried to squash commits but had no luck. Apparently we'll have to leave 3 commits in the PR.
It still doesn't look to be working quite right to me - ex..
@celenity wrote in #262 (comment):
It still doesn't look to be working quite right to me - ex..
See https://codeberg.org/ivankopylov6603/Phoenix/src/branch/lfs/linux-flatpak/assets/phoenix.png
Perhaps the problem is that you are looking at the commit, but I was looking at the fork branch and after the merge everything will be fine?
Edit: add text
@ivankopylov6603 wrote in #262 (comment):
@celenity wrote in #262 (comment):
It still doesn't look to be working quite right to me - ex..
See https://codeberg.org/ivankopylov6603/Phoenix/src/branch/lfs/linux-flatpak/assets/phoenix.png
Interesting, I'm guessing it's just a bug with Forgejo and specific to the view in the MR then?
Since it looks good in your branch directly, I'll go ahead and merge (since it'll be in the dev branch, we can still make changes if we find it causes issues), thank you for your time/work here!
Yep, looks good after merging!
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?