Woodpecker 2.7.1 reporting "an unknown error occured" in repo settingswoodpecker-ci/woodpecker · updated6 months ago · 27% similar bug
agent connection seems broken, rpc access token expiredwoodpecker-ci/woodpecker · updated6 months ago · 27% similar bug
External configuration for pipelines is no longer working since 2.4.0woodpecker-ci/woodpecker · closed11 months ago · 30% similar duplicate
Linter errors on repos dependent on external configuration APIwoodpecker-ci/woodpecker · closed13 months ago · 29% similar bug
Starting a simple stack result in "forge not configured"woodpecker-ci/woodpecker · closed6 months ago · 28% similar bug
woodpecker next agent stopped running jobs: `cannot unmarshal array into Go struct field Config.config.network of type types.Network`woodpecker-ci/woodpecker · closed3 months ago · 28% similar bug
Local agent panic, better parse WOODPECKER_FILTER_LABELS optionwoodpecker-ci/woodpecker · closed24 months ago · 28% similar bug
Updating schema validation in `https://www.schemastore.org/api/json/` to allow `*.yaml`woodpecker-ci/woodpecker · closed27 months ago · 27% similar