NaxGCC-FW/.forgejo/workflows/clippy-check.yml

name: Code quality

on: pull_request

concurrency:
  group: ${{ gitea.ref }}
  cancel-in-progress: true

jobs:
  check:
    runs-on: nix-flakes

    steps:
      - name: Set up packages
        run: |
          echo "extra-substituters = https://builder.naxdy.org/attic" >> /etc/nix/nix.conf
          echo "extra-trusted-public-keys = attic:05LdE8Nav5Qd1E+KOJqSwdr+WE1z8AUmSb3oKL7s8dk=" >> /etc/nix/nix.conf
          nix profile install nixpkgs#nodejs "github:zhaofengli/attic?ref=6eabc3f02fae3683bffab483e614bebfcd476b21"
          echo "PATH=/nix/var/nix/profiles/per-user/root/profile/bin:$PATH" >> "$GITHUB_ENV"
      - uses: actions/checkout@v4
      - name: Run Clippy
        run: |
          nix develop . --command cargo clippy -- -Dwarnings
chore: refactor according to clippy & clean up config (#6) Reviewed-on: https://git.naxdy.org/NaxdyOrg/NaxGCC-FW/pulls/6 2024-04-03 16:53:52 +00:00			`name: Code quality`

			`on: pull_request`

chore: cancel previous clippy runs if need be 2024-04-08 20:40:38 +00:00			`concurrency:`
add mode to further improve input latency while maintaining accuracy (#8) This feels even hackier than consistency mode... we hold off on writing USB reports until the button state actually changes. Passes the input integrity benchmark with ~99.6%, but that doesn't mean much since the challenge is preserving input integrity for inputs less than 8.33ms apart. Current rate limiter looks good from initial measurements, so will probably merge this at some point and leave it up to users to try the mode out or not. For now, I'd still recommend regular consistency mode, it's still hacky, but way less than this. Also, not breaking because the new enum for input consistency mode is backward compatible with the bool. Reviewed-on: https://git.naxdy.org/NaxdyOrg/NaxGCC-FW/pulls/8 2024-04-08 20:53:23 +00:00			`group: ${{ gitea.ref }}`
chore: cancel previous clippy runs if need be 2024-04-08 20:40:38 +00:00			`cancel-in-progress: true`

chore: refactor according to clippy & clean up config (#6) Reviewed-on: https://git.naxdy.org/NaxdyOrg/NaxGCC-FW/pulls/6 2024-04-03 16:53:52 +00:00			`jobs:`
			`check:`
			`runs-on: nix-flakes`

			`steps:`
			`- name: Set up packages`
			`run: \|`
			`echo "extra-substituters = https://builder.naxdy.org/attic" >> /etc/nix/nix.conf`
			`echo "extra-trusted-public-keys = attic:05LdE8Nav5Qd1E+KOJqSwdr+WE1z8AUmSb3oKL7s8dk=" >> /etc/nix/nix.conf`
			`nix profile install nixpkgs#nodejs "github:zhaofengli/attic?ref=6eabc3f02fae3683bffab483e614bebfcd476b21"`
			`echo "PATH=/nix/var/nix/profiles/per-user/root/profile/bin:$PATH" >> "$GITHUB_ENV"`
			`- uses: actions/checkout@v4`
			`- name: Run Clippy`
			`run: \|`
add mode to further improve input latency while maintaining accuracy (#8) This feels even hackier than consistency mode... we hold off on writing USB reports until the button state actually changes. Passes the input integrity benchmark with ~99.6%, but that doesn't mean much since the challenge is preserving input integrity for inputs less than 8.33ms apart. Current rate limiter looks good from initial measurements, so will probably merge this at some point and leave it up to users to try the mode out or not. For now, I'd still recommend regular consistency mode, it's still hacky, but way less than this. Also, not breaking because the new enum for input consistency mode is backward compatible with the bool. Reviewed-on: https://git.naxdy.org/NaxdyOrg/NaxGCC-FW/pulls/8 2024-04-08 20:53:23 +00:00			`nix develop . --command cargo clippy -- -Dwarnings`