Mitch Spano

The supported engines are enumerated in [this file](https://github.com/forcedotcom/sfdx-scanner/blob/dev/src/Constants.ts) within the scanner's source code. Here are the current values which can be accepted as `engine` value for input: - pmd -...

Can we please split this up into more manageable and reviewable chunks? This is too much to review all in one PR.

I cannot accept a PR of this magnitude to the project. This needs to be broken down into smaller chunks.

This pull request is simply far too large for a valid review.

This might be related to an issue with the sfdx scanner cli plugin - see [this issue](https://github.com/forcedotcom/sfdx-scanner/issues/1104) for more details - but I will take a look after work.

@RaviVaranasi Any updates will be reported here. Unfortunatly no progress has been made on this proposed enhancement.

Please sign the CLA so I can review these contributions. https://github.com/mitchspano/apex-trigger-actions-framework/blob/main/docs/contributing.md

This is a very large PR. Can we break it down into smaller changes?

> @mitchspano Done. This is now cosmetic plus an update to the workflow to use `lts/*` since that is the usual Salesforce project standard. > > I can't tell if...

Please sign the CLA so I can review these contributions. https://github.com/mitchspano/apex-trigger-actions-framework/blob/main/docs/contributing.md