Neureka - Codeberg.org

@Zughy wrote in forgejo/forgejo#9550 (comment):

@mfenniak this is why I and many others have been pushing to have it tied to either repositories or even better per package.

@Gusted wrote in forgejo/forgejo#5388 (comment):

@Gusted wrote in forgejo/forgejo#5388 (comment):

@ramones wrote in forgejo/forgejo#3577 (comment):

I’m really disappointed that this was closed. Forgejo was always so good at pushing secure software, and this current design is not secure due to the unintuitive nature. Most end users do not...

Scoping packages to the organization/user instead of the repository creates a mismatch between visibility and access that most users won’t expect.

@RokeJulianLockhart wrote in forgejo/forgejo#9550 (comment):

An API endpoint to quickly check and update this setting on mirrors would also be nice, but that probably deserves it's own feature request.

@aahlenst my only problem with the mentioned capabilities_descriptor is now I have to configure something in the UI for every repo. GitLab forced that on us to schedule workflows. I hate that so...

Personally, I think we need to try and stay backwards compatible with GitHub. That’s one of the strengths we have going with actions and workflows and I’d hate to break that.

@mbugua wrote in forgejo/forgejo#2809 (comment):

Was this ever cherry picked and merged into forgejo? I didn't see anything in the docs.

@infinoid wrote in forgejo/docs#1178 (comment):

Although... I think passing it an old_app.ini and new_app.ini would have made the process much...

@infinoid wrote in forgejo/docs#1178 (comment):

Ideally the migration tooling should respect the app.ini configuration.

I think the migrate-stor...

This really should be documented. Ideally the migration tooling should respect the app.ini configuration.

It was nice to be able to authenticate using Forgejo's OAuth screen when logging in via the git cli, but now I have to push or pull twice every time I start working on something. Same error in the...