6543

drone example:  I also would add a manual "play-button" to trigger it manually next to delete icon

https://pkg.go.dev/github.com/robfig/cron?utm_source=godoc#hdr-Usage

https://github.com/woodpecker-ci/woodpecker/pull/934 is ready enouth ... only docu is missing example: - https://ci.codeberg.org/6543/ci-cron-example/build/2/3 - https://codeberg.org/6543/ci-cron-example/src/branch/main/.woodpecker.yml 

I also would mention gitea public instances... (https://codeberg.org, https://gitea.com, ...) One way to "solve" this multi account problem would be to have a own account you have to create at...

// GitHub API docs: https://docs.github.com/en/rest/pulls/pulls#list-pull-requests-files

one or two api calls to this endpoint as test in integration tests would be nice ... ... api regressions do happen if we dont do this

beside missing test's (and the undocumented option) i would say it's ok ...

Adding the specific sha can be done later...

I would just create & initialize a new repo for the test via api and delete it afterwards

☝️ that s my view too