woodpecker-ci / woodpecker

Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.

https://woodpecker-ci.org

Apache License 2.0

4.07k stars 351 forks source link

Idea: Auto-discover and auto-enable repos with Gitea #2944

Open silverwind opened 8 months ago

silverwind commented 8 months ago

Clear and concise description of the problem

The steps to get Woodpecker running for a repo are quite involved:

If it's a new repo, click "Reload Repositories", so Woodpecker discover the new repo from SCM
Click "Enable" on the repo, which installs the webhook into SCM
Push a .woodpecker.yml to the repo

On other CIs like GitHub Actions it's only one simple step:

Push a .github/workflows/something.yml to the repo

Suggested solution

Provide a way to skip steps 1 and 2 for a better UX.

The SCM could trigger a webhook to Woodpecker on repo creation/deletion/push/tag (System Webhook in Gitea), which is all that Woodpecker would need to work. With such an integration, per-repo webhooks would also become unnecessary.

Validations

[X] Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

qwerty287 commented 8 months ago

Related: https://github.com/woodpecker-ci/woodpecker/issues/71

silverwind commented 8 months ago

71 seems to be for GitHub, my aim here is for Gitea.

qwerty287 commented 8 months ago

Yes, still it's the same idea.