Tested, seems working

Nice work. Im a bit unsure about the sdk. Is it stable enough to rely on it? Does it anything different from the gitea sdk? As long as forgejo is api compatible we could still use the gitea sdk.

Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-3684.surge.sh

forgejo as to be added to cSpell list

Nice work. Im a bit unsure about the sdk. Is it stable enough to rely on it? Does it anything different from the gitea sdk? As long as forgejo is api compatible we could still use the gitea sdk.

It's a fork of the gitea SDK and thus I'd say it's stable. It's not doing that much differently currently except renaming gitea to forgejo.

So man changes 👀

Maybe worth letting the maintainer know that his fork is now being used by WP?

He does already: https://codeberg.org/mvdkleijn/forgejo-sdk/issues/2

Hiya, maintainer of the forgejo sdk here..

Just wanted to let you know that the SDK is indeed a fork of the Gitea SDK. I made the fork after reading about Forgejo's hardfork since I thought that would make sense.

Right now, the fork is the same as the original. I even pulled in the latest updates not too long ago.

I plan to add convenience functions next to functions referencing the Forgejo api 1-on-1.

In general during the course of 1.x you can expect bug fixes, additions and cleanups. The SDK will use semver so if I make backwards incompatible changes, you can expect a major version bump.

I'll probably also add a vanity url for the SDK that people can optionally use so I can move the repo to a different forge if I ever need / want to.

My first order of business though is to make a woodpecker pipeline. I already setup WP locally to test the pipeline since I am new to WP.

Feel free to leave any feedback over at the repo. (sorry for temporarily hijacking this PR with my comment :-p )