Giteabot
e9648f367e
Backport #38010 by @bircni `ifNeedApproval` in `services/actions/notifier_helper.go` decided whether a fork PR's workflow run had to wait for maintainer approval. The bypass clause counted any prior `approved_by > 0` run for `(repo_id, trigger_user_id)`, so the very first Approve-and-run click on a contributor's fork PR permanently trusted that user for every future fork PR in the same repository — including PRs whose only change is the workflow YAML itself. Approving a workflow *run* is not the same as merging *code*. This change aligns the gate with GitHub Actions' first-time-contributor model: trust is granted only after the user has had a pull request merged in the repo. ## Behavior change - **Before**: one approval = permanent trust for that user in that repo. - **After**: every fork PR is gated until the contributor has at least one merged PR in the repo. Existing already-approved runs and merged PRs continue to work; only the trust criterion for *future* fork PRs changes. Maintainers who rely on the implicit "approve once" trust will see the approval banner reappear until they merge a PR from that contributor. --------- Signed-off-by: bircni <bircni@icloud.com> Co-authored-by: bircni <bircni@icloud.com>
mcp-mokogitea-api
@ dbaf91546e
MokoGitea
Custom Gitea fork with enhanced wiki system, DLID licensing, issue statuses, org metadata, CI standardization, and project board API.
Key Features
- Wiki System -- wikilinks, categories, backlinks, template transclusion, revision diffs, rename redirects, folder ACL, enhanced ToC, print view, ZIP export (details)
- DLID Licensing -- license management, entitlements, domain activations, ed25519-signed downloads
- API Token Scope Editing -- edit token scopes via API (PATCH) or web UI after creation
- Issue Statuses -- custom workflow statuses per org with required baseline protection
- Org Metadata -- per-repo metadata API (public GET, admin PUT), platform detection for versioning
- Project Board API -- REST endpoints for project columns and cards
- CI Infrastructure -- reusable workflows, centralized ci-issue-reporter, standardized MOKOGITEA_TOKEN naming
- Dev Deploy Gate -- builds deploy to dev environment first, production checks dev health
Documentation
- Org Wiki -- standards, CLI reference, API docs
- Wiki Features -- all 10 wiki enhancements
- Licensing API
- Repo Wiki -- feature docs, API reference, operations
Contributing
See the org wiki for development guidelines, coding standards, and contribution instructions.
License
This project is licensed under the GNU General Public License v3.0 or later -- see the LICENSE file.