MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 5 Releases 96 Wiki Activity

feat: Dolibarr project auto-creation from repo #57

New Issue
Open
opened 2026-05-08 04:47:37 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-08 04:47:37 +00:00
Owner
Copy Link
Copy Source

Automatically create a Dolibarr project when a new Gitea repo is created.

Flow

  1. New repo created in Gitea
  2. Gitea calls Dolibarr API to create project
  3. Links Dolibarr project ID to repo
  4. Issues in the repo auto-link to the Dolibarr project

Configuration

  • Toggle: auto-create Dolibarr project per org
  • Template: project title pattern (e.g., GITEA-{repo_name})
  • Default task categories from repo labels
  • Assign Dolibarr project manager from repo owner

API

  • POST /repos/{owner}/{repo}/dolibarr/link-project — manual link
  • GET /repos/{owner}/{repo}/dolibarr/project — get linked project
Automatically create a Dolibarr project when a new Gitea repo is created. ## Flow 1. New repo created in Gitea 2. Gitea calls Dolibarr API to create project 3. Links Dolibarr project ID to repo 4. Issues in the repo auto-link to the Dolibarr project ## Configuration - Toggle: auto-create Dolibarr project per org - Template: project title pattern (e.g., `GITEA-{repo_name}`) - Default task categories from repo labels - Assign Dolibarr project manager from repo owner ## API - `POST /repos/{owner}/{repo}/dolibarr/link-project` — manual link - `GET /repos/{owner}/{repo}/dolibarr/project` — get linked project
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Status —
Priority —
Type —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#57
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?