-
### Component
web-ui
### Describe the bug
I have a simple workflow in which I did not specify any `when` block. Woodpecker produces the following lint, which mentions a `when` block:
![when](htt…
-
### Clear and concise description of the problem
as of https://github.com/woodpecker-ci/woodpecker/pull/2691
~~blocked by https://github.com/swaggo/swag/issues/386~~ -> https://github.com/woodpe…
-
### Component
server, agent
### Describe the bug
```yml
labels: # https://woodpecker-ci.org/docs/usage/workflow-syntax#labels
backend: docker
platform: linux/amd64
steps:
python-…
-
### Component
cli
### Describe the bug
Running a pipeline directly like this:
```console
$ woodpecker exec .woodpecker/ubuntu.yml
...
[build:L188:17s] + ./get-deps.sh
[build:L189:17s] /bin/s…
-
### Component
server
### Describe the bug
When the one forgot `commands` directive, then they join to `image` => image cannot be pulled, pipeline stucks.
### Steps to reproduce
1. Creat…
-
### Clear and concise description of the problem
Currently Woodpecker uses the default http user-agent that comes form the go libraries, so all requests from Woodpecker agents shows up as Go-http-cli…
-
The woodpecker cli could get some polishing:
- [x] updater #3382
- [x] background update checker
- [x] update command with `--force` option
- [x] interactive setup #3384
- [x] setup com…
-
### Describe the bug
Somewhat related to " PR triggers the CI twice #2888 ".
To reproduce:
* Create a simple yaml in `main` branch:
```
steps:
test-when:
when:
branch: mai…
-
### Component
agent
### Describe the bug
This is a very intermittent bug that has been hard to track down. We run Woodpecker on GitHub in an [organization protected by organization SAML enforcement…
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Pending Branch Automerge
The…