Additional Apex Classes being added to Deployment Package

[tallenSFDC]

Hello,

I have noticed additional apex classes being added to the deployment package that have a similar API name. For example, If you update a "Logger.cls" apex class, sf-pack is pulling extra apex classes starting with "Logger" like LoggerBatch.cls and LoggerSomethingElse.cls .. exc.
We output the "git diff" command and do not see these classes listed, it seems sf-pack is copying all ".../classes/logger*" files into the deployment package. Witch is most likely ment to grab the required .cls-meta.xml file.

[mmallingSFDC]

@tallenSFDC - can you please define what command you are using?

[tallenSFDC]

Here is the GitHub action step we use

      - name: Generate Delta Package # Generates delta package utilizing sf-pack & git diff
        shell: bash
        run: |
          # Generate delta package using sf-pack
          git --no-pager diff HEAD^ --name-status --no-renames > git-diff.txt
          cat git-diff.txt
          sf source delta git -g git-diff.txt -s ${SOURCE_PACKAGE} -d ${DELTA_PACKAGE}
          sf project generate manifest --source-dir ${DELTA_PACKAGE} --name manifest/deployPackage
          echo "Listing components in delta package..."
          find ${DELTA_PACKAGE} -type f

Here is the output

This is the gitdiff file
git-diff.txt

[mmallingSFDC]

@tallenSFDC - and to confirm - you believe its the
sf source delta git -g git-diff.txt -s ${SOURCE_PACKAGE} -d ${DELTA_PACKAGE}
command that is being greedy and "over copying" files ?

[tallenSFDC]

Correct. In this example we should only have the APLAppealRouter.cls in the deployment package and did not want the APLAppealRouterTest.cls, or APLAppealRouterAction.cls.