Hello there! Long story short. I use Yarn 4, monorepo, and Yarn Workspaces to manage a handful of web projects in a single code base. Every time this action runs, it updates the package.json file and regenerates the yarn.lock file using Yarn 1 specification (instead of my project's Yarn 4) and commit the changes back to the version control. This is an unwanted side-effect that breaks parts of my code. I'd like to see this action commit only necessary files and avoid touching anything else. Is that possible? Thanks.
Hello there! Long story short. I use Yarn 4, monorepo, and Yarn Workspaces to manage a handful of web projects in a single code base. Every time this action runs, it updates the package.json file and regenerates the yarn.lock file using Yarn 1 specification (instead of my project's Yarn 4) and commit the changes back to the version control. This is an unwanted side-effect that breaks parts of my code. I'd like to see this action commit only necessary files and avoid touching anything else. Is that possible? Thanks.