MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 89 Pull Requests 1 Actions Packages Projects Releases 33 Wiki Activity

bug: pull_request events not fired for API-created PRs #220

New Issue
Closed
opened 2026-05-26 19:00:42 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-26 19:00:42 +00:00
Owner
Copy Link
Copy Source

Summary

When a pull request is created via the Gitea API (POST /repos/{owner}/{repo}/pulls), the pull_request: opened event does not fire. This means Actions workflows with on: pull_request: types: [opened] are never triggered for API-created PRs.

PRs created through the web UI do fire the event correctly.

Reproduction

  1. Create a workflow with on: pull_request: types: [opened]
  2. Create a PR via API: POST /api/v1/repos/Org/Repo/pulls
  3. Observe: no workflow run is triggered
  4. Create a PR via web UI for the same branches
  5. Observe: workflow fires correctly

Impact

High — This breaks automated release promotion workflows. Our CI pipeline promotes pre-releases to RC when a draft PR is opened to main. Since most PRs are created programmatically (via CLI tools, automation, Claude Code), the RC promotion step is completely bypassed.

Affected repos

All repos using the Universal Build & Release workflow (auto-release.yml) — currently 37+ repos across MokoConsulting.

Environment

  • Gitea version: 1.26.1+397-g1e1441f8bd
  • Runners: act_runner nightly-dind-rootless (3 instances)

Expected Behavior

API-created PRs should fire the same pull_request webhook events as UI-created PRs, matching GitHub Actions behavior.

Workaround

Currently using workflow_dispatch as a manual fallback, but this defeats the purpose of the automated promotion pipeline.

Related

## Summary When a pull request is created via the Gitea API (`POST /repos/{owner}/{repo}/pulls`), the `pull_request: opened` event does **not** fire. This means Actions workflows with `on: pull_request: types: [opened]` are never triggered for API-created PRs. PRs created through the web UI do fire the event correctly. ## Reproduction 1. Create a workflow with `on: pull_request: types: [opened]` 2. Create a PR via API: `POST /api/v1/repos/Org/Repo/pulls` 3. Observe: no workflow run is triggered 4. Create a PR via web UI for the same branches 5. Observe: workflow fires correctly ## Impact **High** — This breaks automated release promotion workflows. Our CI pipeline promotes pre-releases to RC when a draft PR is opened to main. Since most PRs are created programmatically (via CLI tools, automation, Claude Code), the RC promotion step is completely bypassed. ### Affected repos All repos using the Universal Build & Release workflow (`auto-release.yml`) — currently 37+ repos across MokoConsulting. ## Environment - Gitea version: 1.26.1+397-g1e1441f8bd - Runners: act_runner nightly-dind-rootless (3 instances) ## Expected Behavior API-created PRs should fire the same `pull_request` webhook events as UI-created PRs, matching GitHub Actions behavior. ## Workaround Currently using `workflow_dispatch` as a manual fallback, but this defeats the purpose of the automated promotion pipeline. ## Related - MokoConsulting/moko-platform#155 (RC promotion feature) - MokoConsulting/MokoWaaS#48 (first repo to hit this)
jmiller added the ci-cdpriority: high labels 2026-05-26 19:01:14 +00:00
jmiller commented 2026-05-26 19:49:13 +00:00
Author
Owner
Copy Link
Copy Source

Being worked on in a separate session.

Being worked on in a separate session.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
 pending: testing
Feature implemented but not yet tested with documented proof
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 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
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: bug
type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 upstream
work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels ci-cd priority: high
Milestone
No items
No Milestone
Projects
Clear projects
No projects
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#220
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?