feat: prefer FORGEJO_TOKEN for runtime token #82
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind
Chore
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
4 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/act!82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "xtex/act:forgejo-token"
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?
Tries to get runtime token from FORGEJO_TOKEN. This improves Forgejo branding.
cascading-pr updated at forgejo/runner#390
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?
50dcecd6a5b8b24724f3Can 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 🤔
@xtex gentle ping
It is unnecessary, really, except for the FORGEJO_TOKEN environment variable exposure, which is for branding improvement. Other changes are redundant and removable.
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.
cascading-pr updated at forgejo/runner#390
Please re-open when you have time to work on this 🙏