Code Analyzer Github Action compatible with Metadata format?

[vc4u]

Can Code Analyzer Github Actions run on Github repo hosting Metadata format structured code?

[johnbelosf]

Yes, I don't see why this would be an issue. Do you have a more specific example?

[vc4u]

Actually, I had tried the Code Analyzer v4 Github Action a few months back to be implemented on my repository. At that time, it didn't recognize the structure. So I had to build a yaml workflow file that reads the metadata format structure and convert it to source format and store it temporarily in a folder, scan it and return result from action from that. Pretty lengthy and complex action which did not work too well, so I wanted to just confirm if there is a pre-requisite for using Github Actions, as I'm again trying to look into this in integrating within our repositories for complete analysis as v5 do all kind of scanning too well not just pmd scans. :-)

This is preview of my repo, it is in metadata structure. It contains all metadata formatted components in root of the repo. No package.xml in my repo. Would the code analyzer have any issues in implementing it as Github Action v2 on this kind of repo?

[johnbelosf]

So you're not using a SFDX project? Concrete examples would help in us answering this

[vc4u]

Yes, not using SFDX project structure. The repo is actually attached to Copado Deployment DevOps tool. The Copado tool takes full org metadata and put it in the Github Repositories in Metadata Format. I am looking to run Github Action for Code Analyzer on this repository on Commits.

[stephen-carter-at-sf]

See https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-pmd.html#format-of-metadata-component-files-in-your-salesforce-dx-project where it discusses metadata vs source format.

By default we assume source format. But with some engines you can add additional file extensions to the languages in order to have those files picked up.