Reusable Workflows

A collection of reusable GitHub Actions workflow definitions for the ownCloud organization. These shared workflows standardize CI/CD patterns -- such as linting, testing, building, and deploying -- across multiple ownCloud repositories, reducing duplication and ensuring consistent automation practices.

Getting Started

Follow the steps below to use these workflows in your repository.

Using a Workflow

Reference a workflow from this repository in your GitHub Actions configuration:

jobs:
  build:
    uses: owncloud/reusable-workflows/.github/workflows/<workflow-name>.yml@main
    with:
      # workflow-specific inputs
    secrets:
      # workflow-specific secrets

See the .github/workflows/ directory for available workflow definitions.

Documentation

• GitHub Reusable Workflows

Part of ownCloud Infrastructure

These reusable workflows are referenced by repositories across the ownCloud GitHub organization using the uses: owncloud/reusable-workflows/.github/workflows/<name>@<ref> syntax.

Community & Support

Star this repo and Watch for release notifications!

• ownCloud Website
• Community Discussions
• Matrix Chat
• Documentation
• Enterprise Support
• OSPO Home

Contributing

We welcome contributions! Please read the Contributing Guidelines and our Code of Conduct before getting started.

Workflow

• Rebase Early, Rebase Often! We use a rebase workflow. Always rebase on the target branch before submitting a PR.
• Dependabot: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
• Signed Commits: All commits must be PGP/GPG signed. See GitHub's signing guide.
• DCO Sign-off: Every commit must carry a Signed-off-by line:

  git commit -s -S -m "your commit message"
  

• GitHub Actions Policy: Workflows may only use actions that are (a) owned by owncloud, (b) created by GitHub (actions/*), or (c) verified in the GitHub Marketplace.

Security

Do not open a public GitHub issue for security vulnerabilities.

Report vulnerabilities at https://security.owncloud.com -- see SECURITY.md.

Bug bounty: YesWeHack ownCloud Program

License

See LICENSE for license details.

About the ownCloud OSPO

The Kiteworks Open Source Program Office, operating under the ownCloud brand, launched on May 5, 2026, to steward the open source ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance, community health, and sustainable collaboration between the open source community and Kiteworks, which acquired ownCloud in 2023.

• OSPO Home: https://kiteworks.com/opensource
• GitHub: https://github.com/owncloud
• ownCloud: https://owncloud.com

For questions about the OSPO or licensing, contact ospo@kiteworks.com.

License Migration to Apache 2.0

The OSPO is driving a strategic relicensing of ownCloud repositories toward the Apache License 2.0, following the Apache Software Foundation's third-party license policy.

Individual repositories will migrate as their audit is completed. The LICENSE file in each repo reflects its current license status (not the target).

Current license: Not detected. The OSPO will determine the current license status of this repository before planning any migration steps. If you know the intended license, please open an issue or contact ospo@kiteworks.com.