julia-format icon indicating copy to clipboard operation
julia-format copied to clipboard

Github action for JuliaFormatter.jl

Results 13 julia-format issues
Sort by recently updated
recently updated
newest added

Hi @domluna, thanks for providing JuliaFormatter & this formatting workflow! HowI'm wondering what's the reason behind marking the example in the README as deprecated? The linked https://github.com/julia-actions/julia-format/blob/master/workflows/format_check.yml seems rather more...

I'd like to add a check to ensure that `JuliaFormatter` has been run on PRs submitted to my repo so that contributors (mostly myself) can't merge code that isn't properly...

It would be useful to have an option to print out the diff after showing the names of the files that were formatted. e.g. something like this: https://github.com/JuliaManifolds/Manifolds.jl/blob/9041d2d42315207caab3c8676331235eac9ddc94/.github/workflows/format.yml#L28-L33 This way...

ref #5 Apparently using the JS API makes this much faster and has more capabilities in general.

See https://github.com/LuxDL/Boltz.jl/actions/runs/9477662863/job/26112619818?pr=35#step:2:513. I am seeing similar failures across other repos using this action as well

*JuliaFormatter* action fails and creates a suggestion, but it is identical to the current code: [skipmissing_mean() example](https://github.com/StructuralEquationModels/StructuralEquationModels.jl/pull/203/files#diff-ea8a7b0acfe1d7fc72753c70996ac495392dd0fa8762ff40ab08a6c7f50ed2ec).

Running this action gives the following warning ``` The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@4d4ae6ae148a43d0fd1eda1800170683e9882738, pyTooling/Actions/with-post step@adef08d3bdef092282614f3b683897cefae82ee3. For more info:...

Changes include: - Use `shell: julia --color=yes` to show colored Julia output for steps - Upgrade `julia-actions/cache` to use `v2` - Avoid quoting step names for consistency

The `fail_on_error` argument of the reviewdog action is deprecated. Instead, `fail_level` should be used. See https://github.com/reviewdog/reviewdog/blob/master/CHANGELOG.md#rotating_light-deprecation-warnings

This action doesn't seem to work for PRs from forks, which is quite unfortunate. Such an action is especially useful for occasional contributors who are unfamiliar with the code style...