Move woodpecker-plugins to single forge

[anbraten]

We currently have plugins at:

• 11: https://github.com/orgs/woodpecker-ci/repositories?language=&q=plugin&sort=&type=all
• 16: https://codeberg.org/woodpecker-plugins

To simplify development some maintainers suggested to move all to one place.

Tasks

• [ ] move plugins to decided forge
• [ ] update plugin index to point to new plugins locations

Currently most maintainers seem to be liking the idea to move plugins to codeberg (which would somehow support both forges, core here at github, plugins at codeberg).

[anbraten]

Move to github 👍🏾

[anbraten]

Move to codeberg 👍🏾

[anbraten]

Don't care / plugins can stay at both forges 👍🏾

[anbraten]

Okay, so we will move plugins (apart from plugin-git) to codeberg now:

• [ ] https://github.com/woodpecker-ci/plugin-ready-release-go
• [ ] https://github.com/woodpecker-ci/plugin-surge-preview
• [ ] https://github.com/woodpecker-ci/plugin-deployments
• [ ] https://github.com/woodpecker-ci/plugin-codecov
• [ ] https://github.com/woodpecker-ci/plugin-s3
• [ ] https://github.com/woodpecker-ci/plugin-extend-env
• [x] https://github.com/woodpecker-ci/plugin-prettier
• [ ] https://github.com/woodpecker-ci/plugin-kaniko

[qwerty287]

Maybe we should wait for https://github.com/woodpecker-ci/plugin-ready-release-go/pull/28? This would reduce migration work a lot

[anbraten]

Good point. Will hopefully be included in next Gitea release. So we still have to wait for forgejo and codeberg to update respectively.

[pat-s]

RCs for 1.22 are out, so we can expect this to be unblocked within the next couple of weeks.