feat: Add native integration for OneDev DevOps Platform
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
The payload names no source files or tests, so start by finding the existing Gitea/Forgejo provider code in the repo and the integration settings screen. The issue's example webhook JSON and the POST /api/repositories/{repositoryId}/commits/{commitHash}/statuses endpoint are the concrete contracts to check against. Done would mean a maintainer-agreed design for auth (PAT vs OAuth), state mapping and webhook registration. This is design work, so confirm scope with maintainers before coding.
索引モデルが issue の本文から書いたものです。
説明
Feature Request: Add native integration for OneDev DevOps Platform
Is your feature request related to a problem? Please describe.
Currently, users hosting their source code and CI/CD pipelines on OneDev cannot seamlessly connect their repositories to Windshift. While Gitea and Forgejo enjoy native, out-of-the-box support, OneDev users are forced to rely on complex custom webhooks and REST API workarounds to sync workspaces and trigger automations.
Describe the solution you'd like
We need a native provider integration for OneDev within the Windshift ecosystem. This should include:
- OAuth2 / Personal Access Token Authentication: Easy account linking via OneDev Personal Access Tokens (PAT) or OAuth applications.
- Repository Syncing: The ability to import and track projects directly from a self-hosted OneDev instance.
- Webhook Automation: Automatic registration of webhooks in OneDev to listen for code pushes, pull requests, and issue updates.
- Windshift CLI (
ws) Support: Commands to list, link, and trigger OneDev-backed workspaces natively.
Describe alternatives you've considered
- Managing custom automation via
wsCLI scripts embedded in OneDev CI/CD pipeline steps. - Manually configuring generic inbound webhooks in Windshift, which lacks bidirectional sync and deep repo visibility.
Implementation Details & Requirements
1. Authentication & Connection Layer
- Add a
OneDevProviderconfiguration block to the integration settings. - Required inputs:
Instance URL,Token / OAuth Credentials, andOrganization/User Namespace.
2. Specific Data & Field Mapping
To ensure smooth translation between Windshift objects and OneDev's flexible domain model, the following core schemas must be mapped:
A. State & Status Mapping
Windshift task states must map cleanly to OneDev issue states. Because OneDev allows custom workflows, the integration must default to standard transitions while allowing user overrides:
- Windshift
Backlog/Todo➡️ OneDevOpenstate. - Windshift
In Progress➡️ OneDevIn Progressstate. - Windshift
Done➡️ OneDevClosedstate.
B. User & Identity Resolution
- Map
Windshift.User.EmailorWindshift.User.UsernametoOneDev.User.Nameto correctly handle automated workload assignments and track commit attributions inside workspaces.
3. API Payload & Event Structures
Utilize OneDev's structural REST API to handle lifecycle events. The payload processing engine should support the following specifications:
A. Inbound Webhook Handling (OneDev to Windshift)
The integration endpoint must listen for OneDev event payloads (typically structured around OneDev.Issue or OneDev.PullRequest objects) to trigger workspace syncs:
{
"event": "issue_opened",
"issue": {
"id": 1024,
"number": 42,
"title": "Implement feature X",
"description": "Detailed requirement text...",
"state": "Open",
"submitter": {
"name": "developer_username"
}
},
"repository": {
"id": 56,
"name": "project-repo"
}
}
B. Outbound Status Delivery (Windshift to OneDev)
To reflect Windshift workspace builds and check statuses directly inside the OneDev UI, the provider must send standard status updates to the OneDev commit tracking endpoint:
- Endpoint:
POST /api/repositories/{repositoryId}/commits/{commitHash}/statuses - Payload Structure:
{
"context": "Windshift Workspace Build",
"state": "SUCCESSFUL",
"description": "Windshift environment provisioned successfully.",
"targetUrl": "https://windshift.local"
}
(Valid OneDev states to map: PENDING, RUNNING, SUCCESSFUL, FAILED)
4. User Interface (UI) Components
- Add the OneDev logo to the "Connect a Git Provider" screen alongside GitHub, GitLab, and Gitea.
- Provide clear validation states for self-hosted URLs (e.g., verifying
https://onedev.localconnectivity).
Additional Context
- OneDev Project Home: https://github.com/theonedev/onedev
- This will bridge the gap for users who prefer OneDev's heavy emphasis on built-in Kubernetes CI/CD pipelines over lighter alternatives like Gitea.
- 主要言語
- Go
- スター
- 421
- フォーク
- 50
- 平均マージ
- 17時間 34分
- マージ済み PR(30日)
- 80
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
Windshiftapp/core のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
Windshiftapp/core#542 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
Windshiftapp/core#334 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
Windshiftapp/core#259 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
[Bug][AI chat] Select menu dont appear when on index page対応中かも @valentimarco が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 20/100
Windshiftapp/core#541 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
Windshiftapp/core#538 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
Windshiftapp/core の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
karmada-io/karmada#8101 ·
メンテナーはふだん 1 日以内に返信
-
product:platform
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
Infisical/infisical#9746 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
CrossEntropyFilter raises on zero probabilities and single-class results対応中かも @NopeCharon が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
txn2/mcp-data-platform#2728 ·
メンテナーはふだん 1 日以内に返信
-
effort:s impact:low raised-by:worker risk:low
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
medici-finance/assay#7259 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信