wezterm/.github/workflows/fmt.yml

name: fmt

on:
  pull_request:
    branches:
      - main
    paths:
      - "**/*.rs"
      - ".github/workflows/fmt.yml"
  push:
    branches:
      - main
    paths:
      - "**/*.rs"
      - ".github/workflows/fmt.yml"

jobs:
  check-code-formatting:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: "Install Rust"
        uses: dtolnay/rust-toolchain@nightly
        with:
          components: rustfmt
      - name: Build
        run: |
          source $HOME/.cargo/env
          cargo +nightly fmt --all -- --check
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00			`name: fmt`

			`on:`
			`pull_request:`
			`branches:`
			`- main`
revise fmt workflow triggers 2023-03-16 09:42:34 +03:00			`paths:`
			`- "*/.rs"`
			`- ".github/workflows/fmt.yml"`
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00			`push:`
			`branches:`
			`- main`
revise fmt workflow triggers 2023-03-16 09:42:34 +03:00			`paths:`
			`- "*/.rs"`
			`- ".github/workflows/fmt.yml"`
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00
			`jobs:`
			`check-code-formatting:`
			`runs-on: ubuntu-latest`
			`steps:`
			`- name: Checkout`
ci: actions/checkout 2.4 -> 3 closes: #1855 2022-04-11 04:34:51 +03:00			`uses: actions/checkout@v3`
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00			`- name: "Install Rust"`
Ci toolchain: Do not use actions-rs/toolchain (#3327) * fix(generate-workflows): Do not use actions-rs [actions-rs/toolchain](https://github.com/actions-rs/toolchain) is unsupported: - Has not recieved updates since November 2020 (~2.5 years) - It uses Node.js 12 and GitHub will stop supporting it Summer this year(?) see this [article](https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/). [dtolnay/rust-toolchain](https://github.com/dtolnay/rust-toolchain) is actively supported and its mostly a 1-1 replacement, the differences are: - Uses the minimal profile always, so no need to specify it. - There is no need to override the toolchain. I also removed some things: - None of the generated actions use `rustfmt` so I removed the component - The toolchain is always stable, so I specified it in the action itself instead of in the action parameters. * ci: Regenerate workflows * fix: Remove ALLOW_UNSECURE_COMMANDS from action * fix(CentOS7): Manually install rustup as CentOS7 uses a very old curl * fix: Restart shell so that the rustup command is available * feat: Add exeption to the CentOS workflow to download rustup * fix: Remove actions-rs/toolchain from remaining workflows * fix: Address review comment 2023-03-24 20:16:09 +03:00			`uses: dtolnay/rust-toolchain@nightly`
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00			`with:`
ci: explicitly install rustfmt 2022-01-18 01:14:32 +03:00			`components: rustfmt`
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00			`- name: Build`
			`run: \|`
			`source $HOME/.cargo/env`
encoding my preferred import grouping in the rustfmt config This uses an unstable option in rustfmt, you `cargo +nightly fmt` needs to be used to format the code correctly. 2022-01-17 23:49:44 +03:00			`cargo +nightly fmt --all -- --check`
ci: put fmt check into separate workflow 2022-01-17 05:07:47 +03:00