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

[chore] Why use GITHUB_READ_TOKEN in workflows #11301

New Issue
Closed
opened 2025-11-02 09:33:45 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 09:33:45 -06:00
Owner
Copy Link

Originally created by @harryzcy on GitHub (Jul 22, 2023).

Feature Description

Github automatically adds GITHUB_TOKEN to all actions. Is there a reason why we are using non-standard GITHUB_READ_TOKEN in some of the tests?

I searched around and I guess it's created when still using drone for CI. So we actually could update this?

Screenshots

No response

Originally created by @harryzcy on GitHub (Jul 22, 2023). ### Feature Description Github automatically adds `GITHUB_TOKEN` to all actions. Is there a reason why we are using non-standard `GITHUB_READ_TOKEN` in some of the tests? I searched around and I guess it's created when still using drone for CI. So we actually could update this? ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 09:33:45 -06:00
GiteaMirror commented 2025-11-02 09:33:46 -06:00
Author
Owner
Copy Link

@wolfogre commented on GitHub (Jul 24, 2023):

IIRC, GITHUB_TOKEN is used to checkout the code of Gitea, while GITHUB_READ_TOKEN is used to test migration from GitHub, it has only read access to go-gitea/test_repo. I don't think they're the same thing.

e81ccc406b/services/migrations/github_test.go (L20-L24)

@wolfogre commented on GitHub (Jul 24, 2023): IIRC, `GITHUB_TOKEN` is used to checkout the code of Gitea, while `GITHUB_READ_TOKEN` is used to test migration from GitHub, it has only read access to `go-gitea/test_repo`. I don't think they're the same thing. https://github.com/go-gitea/gitea/blob/e81ccc406bf723a5a58d685e7782f281736affd4/services/migrations/github_test.go#L20-L24
GiteaMirror commented 2025-11-02 09:33:46 -06:00
Author
Owner
Copy Link

@harryzcy commented on GitHub (Jul 27, 2023):

Thanks, closing as it's intended

@harryzcy commented on GitHub (Jul 27, 2023): Thanks, closing as it's intended
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/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#11301
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?