github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-21 03:14:01 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Limiting the act_runner launch area #13314

New Issue
Open
opened 2025-11-02 10:38:19 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 10:38:19 -06:00
Owner
Copy Link

Originally created by @vaerh on GitHub (Jul 22, 2024).

Feature Description

Hi!

I would like to be able to restrict the runners to run for certain branches of the repository. Or using content from .github/... at all, but still be able to run scripts from a branch containing .gitea/workflows.

The problem is specific to synchronizing external repositories that have branches with local changes. It would be very nice if there was a way to only run scripts for a specially designated branch or branches. All others would just be ignored.

In my case, when synchronizing on a schedule, new branches from a upstream repository are added for which autotests, build scripts and so on are immediately run.

Screenshots

No response

Originally created by @vaerh on GitHub (Jul 22, 2024). ### Feature Description Hi! I would like to be able to restrict the runners to run for certain branches of the repository. Or using content from `.github/...` at all, but still be able to run scripts from a branch containing `.gitea/workflows`. The problem is specific to synchronizing external repositories that have branches with local changes. It would be very nice if there was a way to only run scripts for a specially designated branch or branches. All others would just be ignored. In my case, when synchronizing on a schedule, new branches from a upstream repository are added for which autotests, build scripts and so on are immediately run. ### Screenshots _No response_
GiteaMirror added the topic/gitea-actionstype/proposal labels 2025-11-02 10:38:19 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/gitea-actions type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13314
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?