Repository navigation
feat: introduce forgejo - #240
Conversation
Coverage report
Show files with reduced coverage 🔻
Test suite run success230 tests passing in 19 suites. Report generated by 🧪jest coverage report action from 4c80ff3 |
Codeberg is running on Forgejo, however it would be better to advertise compatibility with the underlying software than with this specific deployment.
lampajr
left a comment
There was a problem hiding this comment.
Hey @oliverpool , sorry for the late reply!
(Ideally all references to Codeberg should be removed in favor of Forgejo, but this would be a much bigger undertaking...)
Indeed, as long as Codeberg is feature-equivalent with the base Forgejo and there is no specific customization I agree with this - but this might be slightly trickier as I'd like to be either backward compatible or properly plan in to start a new major version removing codeberg
|
Don't worry about the delay :), yes Codeberg is Forgejo with some minor adjustments (mostly visual). Maybe it should be deprecated (removing it might be too much effort for not much gain). |
Codeberg is running on Forgejo, however it would be better to advertise compatibility with the underlying software than with this specific deployment.
fixes https://code.ffmpeg.org/actions/git-backporting/commit/a7004ff4d9427fc59afcaf21e6d7bdf08f48f861 (cc @BtbN ;)
Description
This add
Forgejoas a git platform (software run by codeberg.org and other organisations).The auto-detection should work when run inside Forgejo Actions.
(Ideally all references to Codeberg should be removed in favor of Forgejo, but this would be a much bigger undertaking...)
How Has This Been Tested?
Running
FORGEJO_SERVER_URL=http://localhost node ./dist/cli/index.jssucceeds (but fails without the env var), when targeting Forgejo (apart from codeberg).Checklist
Merge criteria: