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

Github actions are shown at gitea actions when the reposity is a github mirror. #12771

New Issue
Closed
opened 2025-11-02 10:20:27 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 10:20:27 -06:00
Owner
Copy Link

Originally created by @yekanchi on GitHub (Apr 2, 2024).

Description

if you mirror a repository from Github to Giteaand you have some Github actions. they yml files and some running history of Github actions are show inside the Gitea actions tab, I think it's weird.

Gitea Version

1.22 dev

Operating System

windows

How are you running Gitea?

local

Originally created by @yekanchi on GitHub (Apr 2, 2024). ### Description if you mirror a repository from Github to Giteaand you have some Github actions. they yml files and some running history of Github actions are show inside the Gitea actions tab, I think it's weird. ### Gitea Version 1.22 dev ### Operating System windows ### How are you running Gitea? local
GiteaMirror added the type/bug label 2025-11-02 10:20:28 -06:00
GiteaMirror commented 2025-11-02 10:20:29 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 2, 2024):

I don't think we have migrated the history actions tasks log. Maybe it triggered the actions when migrating.

@lunny commented on GitHub (Apr 2, 2024): I don't think we have migrated the history actions tasks log. Maybe it triggered the actions when migrating.
GiteaMirror commented 2025-11-02 10:20:29 -06:00
Author
Owner
Copy Link

@yekanchi commented on GitHub (Apr 2, 2024):

I don't think we have migrated the history actions tasks log. Maybe it triggered the actions when migrating.

I checked again, yes it's triggered, it's not migrated.

@yekanchi commented on GitHub (Apr 2, 2024): > I don't think we have migrated the history actions tasks log. Maybe it triggered the actions when migrating. I checked again, yes it's triggered, it's not migrated.
GiteaMirror commented 2025-11-02 10:20:29 -06:00
Author
Owner
Copy Link

@yekanchi commented on GitHub (May 30, 2024):

this is an example , a mirror repository of cache actions in local gitea casues actions to show up. whie the local repository has disabled actions.
image

image

@yekanchi commented on GitHub (May 30, 2024): this is an example , a mirror repository of cache actions in local gitea casues actions to show up. whie the local repository has disabled actions. ![image](https://github.com/go-gitea/gitea/assets/25511175/ce28fcb2-b3de-4f21-b42b-808834400b47) ![image](https://github.com/go-gitea/gitea/assets/25511175/0ae96835-106d-4655-b96c-d4b6c2ffc544)
GiteaMirror commented 2025-11-02 10:20:29 -06:00
Author
Owner
Copy Link

@Zettat123 commented on GitHub (Sep 29, 2024):

This is weird. I noticed that there are some scheduled workflows in this repository. I guess some of the scheduled workflows might be running after the migration and before disabling Actions.

And I agree that we should disable Actions for mirror repositories by default (#30350)

@Zettat123 commented on GitHub (Sep 29, 2024): This is weird. I noticed that there are some scheduled workflows in this repository. I guess some of the scheduled workflows might be running after the migration and before disabling Actions. And I agree that we should disable Actions for mirror repositories by default (#30350)
GiteaMirror commented 2025-11-02 10:20:29 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Oct 15, 2024):

I have same problem.

@somera commented on GitHub (Oct 15, 2024): I have same problem.
GiteaMirror commented 2025-11-02 10:20:30 -06:00
Author
Owner
Copy Link

@Zettat123 commented on GitHub (Nov 13, 2024):

You can use the doctor command added in #32424 to disable "Actions" unit for mirrors.

@Zettat123 commented on GitHub (Nov 13, 2024): You can use the doctor command added in #32424 to disable "Actions" unit for mirrors.
GiteaMirror commented 2025-11-02 10:20:30 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Nov 13, 2024):

You can use the doctor command added in #32424 to disable "Actions" unit for mirrors.

This can be used with the next release?

At the moment I'm using own python script which makes an REST-API Call for affected mirrors.

@somera commented on GitHub (Nov 13, 2024): > You can use the doctor command added in #32424 to disable "Actions" unit for mirrors. This can be used with the next release? At the moment I'm using own python script which makes an REST-API Call for affected mirrors.
GiteaMirror commented 2025-11-02 10:20:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 13, 2024):

I think it can be backported to v1.22. I have added the backport label, a new backport PR will be created later.

@lunny commented on GitHub (Nov 13, 2024): I think it can be backported to v1.22. I have added the backport label, a new backport PR will be created later.
GiteaMirror commented 2025-11-02 10:20:31 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Nov 26, 2024):

@lunny I installed 1.22.4 and when I add new mirror I see activated actions again.

@somera commented on GitHub (Nov 26, 2024): @lunny I installed 1.22.4 and when I add new mirror I see activated actions again.
GiteaMirror commented 2025-11-02 10:20:31 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 26, 2024):

Sorry, I think this hasn't been backported to v1.22.4 @Zettat123

@lunny commented on GitHub (Nov 26, 2024): Sorry, I think this hasn't been backported to v1.22.4 @Zettat123
GiteaMirror commented 2025-11-02 10:20:31 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Nov 26, 2024):

It's ok. ;) I have my python script to patch this. ;)

@somera commented on GitHub (Nov 26, 2024): It's ok. ;) I have my python script to patch this. ;)
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 type/bug
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#12771
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?