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

feat: Dolibarr webhook events — sync issue lifecycle to CRM #54

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

Push Gitea events to Dolibarr via webhooks.

Events to Sync

Gitea Event Dolibarr Action
Issue created Create task in linked project
Issue closed Mark task as completed
Issue labeled 'billable' Create intervention line
PR merged Update project progress
Release published Create supplier invoice line
Time tracked Add time spent to Dolibarr task

Implementation

  • New webhook event type: dolibarr_sync
  • Configurable mapping rules per repo
  • Dolibarr API client built into Gitea
  • Two-way sync option (Dolibarr changes reflect back)

Configuration

[dolibarr]
ENABLED = true
API_URL = https://crm.mokoconsulting.tech/api/index.php
API_KEY = your-dolibarr-api-key
DEFAULT_PROJECT = 0
SYNC_TIME_TRACKING = true
Push Gitea events to Dolibarr via webhooks. ## Events to Sync | Gitea Event | Dolibarr Action | |---|---| | Issue created | Create task in linked project | | Issue closed | Mark task as completed | | Issue labeled 'billable' | Create intervention line | | PR merged | Update project progress | | Release published | Create supplier invoice line | | Time tracked | Add time spent to Dolibarr task | ## Implementation - New webhook event type: `dolibarr_sync` - Configurable mapping rules per repo - Dolibarr API client built into Gitea - Two-way sync option (Dolibarr changes reflect back) ## Configuration ```ini [dolibarr] ENABLED = true API_URL = https://crm.mokoconsulting.tech/api/index.php API_KEY = your-dolibarr-api-key DEFAULT_PROJECT = 0 SYNC_TIME_TRACKING = true ```
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
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#54
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?