Suggestion: Change the build command from pipenv install --dev --system --deploy to pipenv install --categories="dev-packages packages" --system --deploy

[unesmu]

Currently in the Install dependencies step of this GitHub action the command pipenv install --dev --system --deploy is used.

This will by default install all package categories in the Pipfile, which means it will install package categories other than the [packages] and the [dev-packages] one.

One could have some build categories in the Pipfile such as [packages-mac] and [dev-packages-mac] that are only used for development.

In this scenario, those build categories are not intended to be built in the GitHub action as it is a Linux machine and the categories include macos dependencies.

What I suggest is to use the command pipenv install --categories="dev-packages packages" --system --deploy instead, which will only install the dev-packages and packages categories from the pipfile.

More about package categories here

Potential issues with my suggestion:
In case someone wanted to organize their packages in the Pipfile differently, and have different categories other than packages and dev-packages , but still wants to install them all when building their environment.

PR #8 implements this suggestion.