dotnet-format
dotnet-format copied to clipboard
A GitHub Action to run dotnet-format as part of your workflow
Note the output of the run, some deprecated options of `dotnet-format` are used: ``` Run xt0rted/dotnet-format@v1 Checking 7 files /usr/bin/dotnet format --check --dry-run --files _somefiles_ The `--files` option is deprecated....
I am running `dotnet format` and then trying to commit and push the changes. I can see that the format step updates some files but somehow the commit step doesn't...
I spent past hour or so trying to get `dotnet format` working in my action pipeline for a .NET Core v6 project. I went through various configurations to the `yml`...
``` Run xt0rted/dotnet-format@v1 with: repo-token: *** action: check fail-fast: true env: DOTNET_ROOT: /home/runner/.dotnet /home/runner/.dotnet/dotnet format --check --dry-run The file '--dry-run' does not appear to be a valid project or solution...
I am seeing similar to the `nothing to commit, working tree clean` issue here: https://github.com/xt0rted/dotnet-format/issues/10#issuecomment-598464578, and it does not seem to be due to line-ending settings I made a PR,...
Not sure if I did something wrong implementing the example yaml or this is a legit bug. Run xt0rted/[email protected] with: repo-token: *** action: check fail-fast: true /usr/bin/dotnet format --check --dry-run...
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.0.4 to 5.3.3. Release notes Sourced from typescript's releases. TypeScript 5.3.3 For release notes, check out the release announcement. For the complete list of fixed issues, check...
Bumps [@actions/github](https://github.com/actions/toolkit/tree/HEAD/packages/github) from 5.1.1 to 6.0.0. Changelog Sourced from @actions/github's changelog. 6.0.0 Support the latest Octokit in @actions/github #1553 Drop support of NodeJS v14, v16 Commits See full diff in...
Bumps [semver](https://github.com/npm/node-semver) from 7.3.5 to 7.5.4. Release notes Sourced from semver's releases. v7.5.4 7.5.4 (2023-07-07) Bug Fixes cc6fde2 #588 trim each range set before parsing (@lukekarrys) 99d8287 #583 correctly parse...