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.
chore: make public api consistent
2024-09-03 17:32:04 +01:00 · 2024-09-03 16:41:39 +01:00
1 changed files with 5 additions and 1 deletions
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@ -29,7 +29,11 @@ jobs:
        uses: actions/checkout@v4
      - name: Run stylua
-        run: npx @johnnymorganz/stylua-bin --check .
+        uses: JohnnyMorganz/stylua-action@v4.0.0
        with:
          token: ${{ secrets.GITHUB_TOKEN || secrets.GH_TOKEN  }}
          version: latest
          args: --check .
  cargo-format:
    name: Cargo Format
Author	SHA1	Message	Date
Ade Attwood	386e972834	ci: use GI_TOKEN so we can run ci on other platforms Some checks failed CI / Luacheck (pull_request) Successful in 23s Details CI / Cargo Format (pull_request) Successful in 18s Details CI / Build and test (pull_request) Successful in 1m53s Details Conventional Tools Commitlint / Commitlint (pull_request) Successful in 5s Details CI / StyLua (pull_request) Failing after 3s Details 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
Ade Attwood	8a7d510cda	chore: make public api consistent Some checks failed CI / Luacheck (pull_request) Successful in 22s Details CI / StyLua (pull_request) Failing after 4s Details CI / Cargo Format (pull_request) Successful in 18s Details CI / Build and test (pull_request) Successful in 1m50s Details Conventional Tools Commitlint / Commitlint (pull_request) Successful in 5s Details Summary: Right now we have two ways to access the public api we have `require('ivy')` and `vim.ivy. Each way has a different api that will cause some confusion. Now both apis are the same so anyone that wants to integrate with ivy can do so without having to figure out what one they need to use. Test Plan: The unit tests cover most of the work, I have also been using this locally for quite some time now with now issues.	2024-09-03 16:41:39 +01:00