ci: use GI_TOKEN so we can run ci on other platforms
Some checks failed
CI / Luacheck (pull_request) Successful in 23s
CI / Cargo Format (pull_request) Successful in 18s
CI / Build and test (pull_request) Successful in 1m53s
Conventional Tools Commitlint / Commitlint (pull_request) Successful in 5s
CI / StyLua (pull_request) Failing after 3s
Some checks failed
CI / Luacheck (pull_request) Successful in 23s
CI / Cargo Format (pull_request) Successful in 18s
CI / Build and test (pull_request) Successful in 1m53s
Conventional Tools Commitlint / Commitlint (pull_request) Successful in 5s
CI / StyLua (pull_request) Failing after 3s
Summary: Starting to have a play with forgejo, on this platform you cannot define secrets that have a prefix of `GITHUB_`. I still want to maintain CI on github for any pull requests that may come in. The plan in to use the `GITHUB_TOKEN` when we are running on github and use the `GH_TOKEN` when we are running on forgejo Test Plan: Run the CI on github and forgejo, this will need to be a manual process to validate this works.
This commit is contained in:
parent
8a7d510cda
commit
386e972834
1 changed files with 1 additions and 1 deletions
2
.github/workflows/ci.yml
vendored
2
.github/workflows/ci.yml
vendored
|
|
@ -31,7 +31,7 @@ jobs:
|
|||
- name: Run stylua
|
||||
uses: JohnnyMorganz/stylua-action@v4.0.0
|
||||
with:
|
||||
token: ${{ secrets.GITHUB_TOKEN }}
|
||||
token: ${{ secrets.GITHUB_TOKEN || secrets.GH_TOKEN }}
|
||||
version: latest
|
||||
args: --check .
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue