Repository that hold Woodpecker CI workflows Pandora organization
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
renovate-bot 0da1e89cb0
All checks were successful
ci/woodpecker/push/workflow_push Pipeline was successful
ci/woodpecker/cron/vulnerability Pipeline was successful
ci/woodpecker/cron/auto_merge Pipeline was successful
ci/woodpecker/cron/renovate Pipeline was successful
maint: Update code.thinkaboutit.tech/pandora/workflow-checker.woodpecker Docker tag to v0.1.5 #97
Merged automatically
2026-08-06 15:21:05 +00:00
workflows maint: Update code.thinkaboutit.tech/pandora/workflow-checker.woodpecker Docker tag to v0.1.5 #97 2026-08-06 15:21:05 +00:00
README.md initial commit 2026-05-24 22:48:14 +02:00
renovate.json ci: Use central renovate.json (#73) 2026-07-19 12:01:48 +00:00

Woodpecker Configuration Server

Woodpecker CI has an ability to use a server as external configuration server, see in document. This application start an endpoint that can receive signal from Woodpecker server and respond accordingly.

Structure of workflows

My repositories are organized with a unique suffix, for example:

  • foo.goapp: This is an application written in Go
  • foo.gopack: Package for Go project
  • foo.woodpecker: Woodpecker CI configuration

The workflows can be found in the workflows directory. Each directory is checked as suffix. The directory contains further directories which are events. And those directories contains the workflows.