-
Since we are considering splitting out our container files into smaller bash scripts (rather than doing inline bash), I think it would be helpful to have a code analysis tool to help with consistency …
-
### Type of issue
Bug (unexpected behavior).
### Description
Hi! First, this project is great. TYSM for making/maintaining it.
Second, I'm hitting some unexpected behavior with this GitHub…
-
## New Issue Checklist
- [x] Using the latest version of azohra/shell-linter
- [x] Able to reproduce error multiple times
- [x] Provided information about the bug
- [x] Attached additional infor…
-
### Type of issue
Bug Report
### Description
If by mistake, one forgets to use `fetch-depth: 0` with `actions/checkout@v4`, the action `redhat-plumbers-in-action/differential-shellcheck@v5` w…
-
ShellCheck can suggest a possible solution of the reported defect. Unfortunately, this data isn't available in `gcc` format. It would be nice if `csdiff` could parse ShellCheck JSON format, which cont…
-
### Type of issue
Feature Request
### Description
It would be nice to show more details when differential-shellcheck is run in DEBUG mode.
Ideas:
* Show list of changes - using `` synta…
-
## The config
```
- uses: DeterminateSystems/nix-installer-action@main
with:
extra-conf: |
post-build-hook = ${{ github.workspace }}/post-build-hook.sh
```
…
-
Type: Bug
# Behaviour
At least the "Add Import" code quick fix action is not working if the current file is loacted in a directory excluded in the Pyright pyrightconfig.json configuration file of …
-
It takes a some scanning to actually parse the prompt of available options as you're reviewing a package for merge or build, due to how long and wordy it can get:
```
[D]=view upstream changes sin…
-
```
$ shellcheck -h
...
-e CODE1,CODE2.. --exclude=CODE1,CODE2.. Exclude types of warnings
```
E.g. `shellcheck -e SC1004,SC1083 ...`