feat: Add native integration for OneDev DevOps Platform
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Go
- Stars
- 421
- Forks
- 50
- Avg merge
- 17h 34m
- Merged PRs (30d)
- 80
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Windshiftapp/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Windshiftapp/core#542 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Windshiftapp/core#334 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Windshiftapp/core#259 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Bug][AI chat] Select menu dont appear when on index pagePossibly taken @valentimarco claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
Windshiftapp/core#541 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Windshiftapp/core#538 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in Windshiftapp/core
Similar issues
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
fullsend-ai/fullsend#9733 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
karmada-io/karmada#8101 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day