This adds a very simple example to lint a project with REUSE.
The fsfe/reuse base image is just alpine with the reuse-tool installed.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/57
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Thiago Sueto <herzenschein@gmail.com>
Co-committed-by: Thiago Sueto <herzenschein@gmail.com>
The previous one no longer receives updates
Signed-off-by: Daniel Buck <daniel.buck@mmmgroup.com>
Co-authored-by: Daniel Buck <daniel.buck@mmmgroup.com>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/55
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Tealk <tealk@noreply.codeberg.org>
Co-committed-by: Tealk <tealk@noreply.codeberg.org>
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| mstruebing/editorconfig-checker | major | `2.7.2` -> `v3.0.1` |
---
### Configuration
📅 **Schedule**: Branch creation - "every weekend" (UTC), Automerge - "before 4am" (UTC).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNDAuNSIsInVwZGF0ZWRJblZlciI6IjM3LjM0MC41IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmN5Il19-->
Co-authored-by: woodpecker-bot <woodpecker-bot@obermui.de>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/52
Co-authored-by: Dependency bot <renovate-bot@noreply.codeberg.org>
Co-committed-by: Dependency bot <renovate-bot@noreply.codeberg.org>
I had to sort the entries in the README table to be able to insert my own in alphabetical order.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/51
Co-authored-by: Stefano Volpe <foxy@teapot.ovh>
Co-committed-by: Stefano Volpe <foxy@teapot.ovh>
This PR adds an example Woodpecker pipeline for testing a package written in Julia.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/50
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Andreas Theodosiou <atheodosiou@protonmail.ch>
Co-committed-by: Andreas Theodosiou <atheodosiou@protonmail.ch>
This example adds a matrix step for the 4 most recent supported PHP versions. It uses a bash command and the PHP built-in linter to find errors. It doesn't print much output due to the nature of the linter, but the build step fails with exit code 1 if linting fails.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/40
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Martijn de Boer <git@sexybiggetje.nl>
Co-committed-by: Martijn de Boer <git@sexybiggetje.nl>
Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
---
### Detected Package Files
* `Golang/.woodpecker/Dockerfile` (dockerfile)
* `.woodpecker.yaml` (woodpecker)
### Configuration Summary
Based on the default config's presets, Renovate will:
- Start dependency updates only once this onboarding PR is merged
- Enable Renovate Dependency Dashboard creation.
- Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
- Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
- Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
- Run lock file maintenance (updates) early Monday mornings.
- Schedule automerge daily.
- Schedule for weekends.
- Run Renovate on following schedule: every weekend
🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs.
---
### What to Expect
With your current configuration, Renovate will create 1 Pull Request:
<details>
<summary>chore(deps): update woodpeckerci/woodpecker-cli docker tag to v2.3.0</summary>
- Schedule: ["every weekend"]
- Branch name: `renovate/woodpeckerci-woodpecker-cli-2.x`
- Merge into: `main`
- Upgrade [woodpeckerci/woodpecker-cli](https://github.com/woodpecker-ci/woodpecker) to `v2.3.0-alpine`
</details>
---
❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).
---
This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-config-hash:94693a990c975907e7f13da3309b9d56ba02b3983519b41786edf5cf031e457c-->
Co-authored-by: woodpecker-bot <woodpecker-bot@obermui.de>
Co-authored-by: pat-s <patrick.schratz@gmail.com>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/43
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Dependency bot <renovate-bot@noreply.codeberg.org>
Co-committed-by: Dependency bot <renovate-bot@noreply.codeberg.org>
A pipeline to build a Typst document and push the resulting pdf to some Codeberg repository (for use in Codeberg pages).
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/37
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Stefano Volpe <foxy@teapot.ovh>
Co-committed-by: Stefano Volpe <foxy@teapot.ovh>
Hi. Here’s one more Python example. It makes use of [pdoc](https://pdoc.dev) in order to generate the API documentation for python modules. The docs are then pushed on a pages branch and normally served by codeberg pages.
Co-authored-by: mononym <mononym@riseup.net>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/18
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: mononym <mononym@noreply.codeberg.org>
Co-committed-by: mononym <mononym@noreply.codeberg.org>
This ensures that the provided example won't use version 2 of the plugin if it were to make breaking changes.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/36
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Kamila Borowska <kamila@borowska.pw>
Co-committed-by: Kamila Borowska <kamila@borowska.pw>
I've made a plugin to ease deployment of Codeberg Pages, and figured I would update one of examples to use it.
Tested that this works on https://ci.codeberg.org/repos/12946/pipeline/3.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/35
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Kamila Borowska <kamila@borowska.pw>
Co-committed-by: Kamila Borowska <kamila@borowska.pw>
Within the Hugo workflow, the commit message was built interpolating the `CI_BUILD_CREATED` builtin Woodpecker variable. I believe it is not defined (anymore?): https://woodpecker-ci.org/docs/usage/environment. The most similar thing I have found is `CI_PIPELINE_CREATED`, but I can't get any value beside 0 out of it when using this pipeline. So I propose we use `CI_COMMIT_SHA`, which I already tested in one of my personal projects: https://ci.codeberg.org/repos/12701/pipeline/19/1.
I believe `CI_COMMIT_SHA` is the ideal unique identifier for pipeline triggered by push actions.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/34
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Stefano Volpe <stefano.volpe@student.uva.nl>
Co-committed-by: Stefano Volpe <stefano.volpe@student.uva.nl>
When this example is used will a separate run be triggered in Codeberg CI, which only results in a failed run that never was needed.
I first tried with a file configuration to only trigger on main branch, but that didn't work, so I now opted in to simply add a `[SKIP CI]` at the end of the commit message to make Codeberg CI ignore this commit.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/32
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Andre601 <andre601@noreply.codeberg.org>
Co-committed-by: Andre601 <andre601@noreply.codeberg.org>
An example to publish pages built with mdbook on Codeberg Pages.
Co-authored-by: Tealk <tealk@rollenspiel.monster>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/29
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Tealk <tealk@noreply.codeberg.org>
Co-committed-by: Tealk <tealk@noreply.codeberg.org>
In this example, I demonstrate how to create useful automation for KiCad hardware projects. The Pipeline can be seen running in
https://codeberg.org/ccoenen/Codeberg-KiCad-KiBot-Example
or in a modified form in
https://codeberg.org/ccoenen/Dustbuster-Communicator
---
The automation uses "KiBot", to generate common production files. KiBot can do much more, but I limited this demo to gerber files (used in PCB manufacturing) ibom (used to know which components to place where) and a schematic PDF. It is very likely that projects will want to heavily modify this part of the config anyway, so I only include a starting point.
This example _also_ demonstrates how to add the resulting files to the "packages" facility.
Co-authored-by: amenthes <opensource@amenthes.de>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/26
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Claudius Coenen <ccoenen@noreply.codeberg.org>
Co-committed-by: Claudius Coenen <ccoenen@noreply.codeberg.org>
Example to check [Standard ML](https://www.smlnj.org/sml.html) files recursively, in a given directory, to make sure they execute without problems.
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/25
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Stefano Volpe <stefano.volpe2@studio.unibo.it>
Co-committed-by: Stefano Volpe <stefano.volpe2@studio.unibo.it>
I've been able to successfully make a NodeJS based CI solution to build pages for a static site using eleventy ([11ty.dev](https://11ty.dev)).
## Overview
This process will make use of the following
- Source repo to contain the source code
- Destination repo that will be used to serve the pages
- Codeberg CI (early access)
- Secrets within the CI
## How it works
Currently the `.Woodpecker.yml` file will live in your source codes repo, and have the build commands. Find more [here](https://codeberg.org/cjerrington/eleventy-base-blog-source/src/branch/main/.woodpecker.yml).
For the CI we will start by using the node image, setup the secrets, and build commands.
The use of secrets keeps your information secured and only accessed by the build system. This is beneficial for the email and access token. During the build, the pipeline will clone the source repo, then move into our commands.
We will use the default build dir by 11ty of `_site`. The pipeline will clone our destination repo as _site, then set the remote url for the push after we run our install and build. Once built, it will change directory to the build site and perform our commit and push.
## Accessing the site
On the remote repo we need the default repo to be named pages. This is also houw [Codeberg Pages](https://docs.codeberg.org/codeberg-pages/) setups up the access to what serves the pages we just built. You can follow their documentation on how to access your build site based on `username.codeberg.page`.
Co-authored-by: Clayton Errington <me@claytonerrington.com>
Co-authored-by: 6543 <6543@obermui.de>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/23
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Clayton Errington <cjerrington@noreply.codeberg.org>
Co-committed-by: Clayton Errington <cjerrington@noreply.codeberg.org>
An example of pipeline which builds and deploys an `mkdocs` site to codeberg pages.
This is tested and works in https://codeberg.org/openfindata/openfindata.
Co-authored-by: Laurent Savaëte <laurent@where.tf>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/24
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: laurents <laurents@noreply.codeberg.org>
Co-committed-by: laurents <laurents@noreply.codeberg.org>
- fix: fatal: destination path '/tmp' already exists and is not an empty directory
- fix: .domains should be copied to repo folder not to hugo output folder
- feat: git commit message must not contain CI SKIP when pages branch is excluded from pipeline
Co-authored-by: Peter Prumbach <mail@peterprumbach.de>
Reviewed-on: https://codeberg.org/Codeberg-CI/examples/pulls/16
Co-authored-by: Peter Prumbach <ptpu@noreply.codeberg.org>
Co-committed-by: Peter Prumbach <ptpu@noreply.codeberg.org>
