MokoConsulting/MokoGIT
1
0
Fork 0
Code Issues 146 Pull Requests Releases 96 Wiki Activity

fix(actions): reject workflow_dispatch for workflows without that trigger (#37660) #381

New Issue
Closed
opened 2026-06-01 08:00:39 +00:00 by mokogit-actions · 1 comment
mokogit-actions bot commented 2026-06-01 08:00:39 +00:00
Copy Link
Copy Source

Summary

Upstream bug fix merged into release/v1.26.

Upstream Reference

Severity: Medium

Action

Cherry-pick from upstream release/v1.26 branch.

Auto-created by upstream-bug-sync workflow
Authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com

## Summary Upstream bug fix merged into `release/v1.26`. ## Upstream Reference - PR: https://github.com/go-gitea/gitea/pull/37895 - Merged: 2026-05-29 - Branch: release/v1.26 ## Severity: Medium ## Action Cherry-pick from upstream `release/v1.26` branch. --- *Auto-created by upstream-bug-sync workflow* *Authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>*
mokogit-actions bot added the upstream label 2026-06-01 08:00:39 +00:00
jmiller commented 2026-06-27 02:42:05 +00:00
Owner
Copy Link
Copy Source

Cherry-picked in fix/v1262-security-cherrypicks (commit 8bf445e86a). Closing.

Cherry-picked in `fix/v1262-security-cherrypicks` (commit `8bf445e86a`). Closing.
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
 feature: wiki
Wiki system enhancements
 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
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels upstream
Priority High
Type Bug
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#381
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?