ivy.nvim/.github
Ade Attwood 386e972834
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
ci: use GI_TOKEN so we can run ci on other platforms
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.
2024-09-03 17:32:04 +01:00
..
ISSUE_TEMPLATE chore: add issue templates 2022-12-28 11:07:04 +00:00
workflows ci: use GI_TOKEN so we can run ci on other platforms 2024-09-03 17:32:04 +01:00