feat: prefer FORGEJO_TOKEN for runtime token #82

Closed
xtex wants to merge 1 commit from xtex/act:forgejo-token into main
Contributor

Tries to get runtime token from FORGEJO_TOKEN. This improves Forgejo branding.

Tries to get runtime token from FORGEJO_TOKEN. This improves Forgejo branding.
Contributor

cascading-pr updated at forgejo/runner#390

cascading-pr updated at https://code.forgejo.org/forgejo/runner/pulls/390
viceice left a comment
Owner

please fill PR description with reason why this is useful

please fill PR description with reason why this is useful
@ -81,3 +81,3 @@
func (c Config) GetToken() string {
token := c.Secrets["GITHUB_TOKEN"]
token := c.Secrets["FORGEJO_TOKEN"]
if c.Secrets["GITEA_TOKEN"] != "" {

I think we should only overwrite the token if not already set?

I think we should only overwrite the token if not already set?
xtex marked this conversation as resolved
xtex force-pushed forgejo-token from 50dcecd6a5
All checks were successful
checks / unit (pull_request) Successful in 43s
checks / integration (pull_request) Successful in 26s
/ cascade (pull_request_target) Successful in 29m44s
to b8b24724f3
All checks were successful
checks / unit (pull_request) Successful in 31s
checks / integration (pull_request) Successful in 30s
/ cascade (pull_request_target) Successful in 39s
2024-12-14 13:35:26 +00:00
Compare
Contributor

Can you please explain why this change is necessary? It is already done in the runner and I don't recall why it would be needed in the ACT fork 🤔

Can you please explain why this change is necessary? It is already done in the runner and I don't recall why it would be needed in the ACT fork 🤔
Contributor

@xtex gentle ping

@xtex gentle ping
Author
Contributor

It is unnecessary, really, except for the FORGEJO_TOKEN environment variable exposure, which is for branding improvement. Other changes are redundant and removable.

It is unnecessary, really, except for the FORGEJO_TOKEN environment variable exposure, which is for branding improvement. Other changes are redundant and removable.
Contributor

Could you split the exposure of the variable to a separate pull request so it can be merged? The behavior change would need testing and is less trivial.

Could you split the exposure of the variable to a separate pull request so it can be merged? The behavior change would need testing and is less trivial.
Contributor

cascading-pr updated at forgejo/runner#390

cascading-pr updated at https://code.forgejo.org/forgejo/runner/pulls/390
Contributor

Please re-open when you have time to work on this 🙏

Please re-open when you have time to work on this 🙏
earl-warren closed this pull request 2025-05-26 05:09:50 +00:00
Commenting is not possible because the repository is archived.
No reviewers
No milestone
No project
No assignees
4 participants
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/act!82
No description provided.