MokoGitea

MokoGitea is your private, fully managed Git hosting service powered by Gitea. Manage repositories, CI/CD pipelines, issues, and wiki documentation.

Read more →

CI/CD with Gitea Actions

Details
Category: MokoGitea
  • Minimum Version: v1.26.1-moko.3
  • Applicable Software: MokoGitea
  • Applicable Version: v1.26.1-moko.3

What are Gitea Actions?

Gitea Actions is MokoGitea's built-in CI/CD system. It uses a workflow syntax compatible with GitHub Actions, so if you've used GitHub Actions before, you'll feel right at home. Moko Consulting manages the runner infrastructure, so you can focus on writing your pipelines.

Creating Your First Workflow

  1. In your repository, create the directory .gitea/workflows/.
  2. Add a YAML file (e.g., ci.yaml) with your workflow definition.
  3. Commit and push — the workflow will run automatically.

Example: Basic CI Pipeline

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install dependencies
        run: npm ci

      - name: Run tests
        run: npm test

Workflow Triggers

Control when workflows run using the on key:

  • push — Run on commits pushed to specified branches.
  • pull_request — Run when PRs are opened, updated, or synchronized.
  • schedule — Run on a cron schedule (e.g., nightly builds).
  • workflow_dispatch — Manually trigger from the MokoGitea UI.

Secrets and Variables

Store sensitive values (API keys, deployment credentials) as repository secrets:

  1. Go to Settings → Actions → Secrets.
  2. Click Add Secret.
  3. Enter a Name and Value.

Reference secrets in your workflow:

steps:
  - name: Deploy
    run: ./deploy.sh
    env:
      API_KEY: ${{ secrets.API_KEY }}

Viewing Workflow Results

Check the Actions tab in your repository to see:

  • A list of all workflow runs with status (success, failure, in progress).
  • Detailed logs for each step.
  • Re-run options for failed workflows.

Common Use Cases

  • Automated testing — Run unit tests on every push or PR.
  • Build and package — Compile code and create release artifacts.
  • Deployment — Deploy to staging or production on merge to main.
  • Linting — Check code style and formatting automatically.

Runner Infrastructure

Moko Consulting manages the Gitea Actions runners for your MokoGitea instance. If you need custom runners (e.g., for specialized build environments or GPU workloads), contact our support team.

Hits: 4

Dolibarr API MCP Server

Details
Category: MokoGitea
  • Minimum Version: v1.26.1-moko.1
  • Applicable Software: MCP Server
  • Applicable Version: v1.0.0

Bridge your AI assistant with Dolibarr ERP/CRM using dolibarr-api-mcp — an 85-tool MCP server for invoices, proposals, orders, products, projects, tasks, contacts, tickets, documents, and more, all directly from Claude Code.

Hits: 7

Read more …

Getting Started: Your Account and First Repository

Details
Category: MokoGitea
  • Minimum Version: v1.26.1-moko.1
  • Applicable Software: MokoGitea
  • Applicable Version: v1.26.1-moko.1

Logging In

Your MokoGitea account is created by your Moko Consulting administrator. To log in:

  1. Navigate to your MokoGitea instance URL (provided by your administrator).
  2. Enter your username and password.
  3. Click Sign In.

If you've forgotten your password, use the Forgot Password link on the login page, or contact your administrator.

The Dashboard

After logging in, you'll see your Dashboard, which shows:

  • Activity Feed — Recent actions from repositories you follow or contribute to.
  • Your Repositories — Quick access to repos you own or have been added to.
  • Organizations — Teams and groups you belong to.

Setting Up Your Profile

  1. Click your avatar in the top-right corner and select Settings.
  2. Update your display name, bio, and avatar.
  3. Optionally add your website and location.
  4. Click Update Profile to save.

Creating Your First Repository

  1. Click the + icon in the top navigation bar and select New Repository.
  2. Enter a Repository Name (e.g., my-first-project).
  3. Add an optional Description.
  4. Choose Private or Public visibility.
  5. Check Initialize this repository to create it with a README file.
  6. Click Create Repository.

Cloning Your Repository Locally

Once your repository is created, clone it to your local machine:

git clone https://your-mokogitea-url/username/my-first-project.git
cd my-first-project

You can also use SSH if you've set up SSH keys.

Making Your First Commit

  1. Create or edit a file in your cloned repository.
  2. Stage and commit your changes: 
    git add .
git commit -m "My first commit"
  3. Push to MokoGitea: 
    git push origin main

Refresh your repository page in MokoGitea to see your changes.

Hits: 5

Gitea API MCP Server

Details
Category: MokoGitea
  • Minimum Version: v1.26.1-moko.1
  • Applicable Software: MCP Server
  • Applicable Version: v1.0.0

Manage your entire MokoGitea instance from Claude Code with gitea-api-mcp — an open-source MCP server that exposes 61 tools for repositories, issues, pull requests, releases, branches, CI/CD, organizations, wikis, and webhooks.

Hits: 5

Read more …

Issues and Project Management

Details
Category: MokoGitea
  • Minimum Version: v1.26.1-moko.1
  • Applicable Software: MokoGitea
  • Applicable Version: v1.26.1-moko.1

Using Issues

MokoGitea's built-in issue tracker helps you report bugs, request features, and manage tasks within each repository.

Creating an Issue

  1. Navigate to your repository and click the Issues tab.
  2. Click New Issue.
  3. Enter a descriptive Title and detailed Description (Markdown is supported).
  4. Optionally assign Labels, a Milestone, and an Assignee.
  5. Click Submit New Issue.

Labels

Labels help categorize issues (e.g., bug, enhancement, documentation). Create and manage labels under Issues → Labels. Use colors and descriptions to keep your team aligned.

Milestones

Milestones group related issues into a release or sprint. Create milestones under Issues → Milestones with a title, description, and optional due date. Track progress via the milestone's completion percentage.

Assigning Issues

Assign issues to team members to clarify ownership. You can assign multiple people to a single issue if collaboration is needed.

Project Boards

MokoGitea supports Kanban-style project boards for visual task management.

  1. Go to the Projects tab in your repository (or organization).
  2. Click New Project and give it a name.
  3. Add columns like To Do, In Progress, and Done.
  4. Drag and drop issues between columns as work progresses.

Linking Issues to Pull Requests

Reference an issue in a pull request or commit message using #issue-number (e.g., Fixes #42). When the pull request is merged, the linked issue will automatically close.

Tips

  • Use issue templates (stored in .gitea/ISSUE_TEMPLATE/) to standardize bug reports and feature requests.
  • Subscribe to issues to receive notifications about updates.
  • Use @mentions to notify specific team members in comments.
Hits: 8
  1. Joomla API MCP Server
  2. Organizations and Teams
  3. Pull Requests and Code Review
  4. Repository Management: Cloning, Forking, and Branching