Describe the user story
Allows a user to exclude files/folders in a global gitignore file instead of copying and pasting the same contents into new gitignore file for each project.
Describe the solution you'd like
Before the migration to berry I worked on a PR to add excluding of files and folders using a global gitignore during the pack process in yarn. The original PR was not re-reviewed and I'm curious would that PR be useful to add in berry to the existing plugin-pack or a new one? I didn't see any similar code during packing in berry currently, so I'd be interested if the community is still open to this or if it's already been implemented in the codebase. Any feedback would be greatly appreciated.
Describe the drawbacks of your solution
The proposed solution adds slight complexity during packing because it requires reading from two different git ignore files, changes to an existing plugin or adding a new one entirely. I think the real problem here comes from human error and someone forgetting that they have ignored files/folders in a git ignore and not another and accidentally excludes the wrong thing.
Describe alternatives you've considered
Two alternatives come to mind: leave the code as is or build this into a new or existing plugin.
Describe the user story
Allows a user to exclude files/folders in a global gitignore file instead of copying and pasting the same contents into new gitignore file for each project.
Describe the solution you'd like
Before the migration to berry I worked on a PR to add excluding of files and folders using a global gitignore during the pack process in yarn. The original PR was not re-reviewed and I'm curious would that PR be useful to add in berry to the existing plugin-pack or a new one? I didn't see any similar code during packing in berry currently, so I'd be interested if the community is still open to this or if it's already been implemented in the codebase. Any feedback would be greatly appreciated.
Describe the drawbacks of your solution
The proposed solution adds slight complexity during packing because it requires reading from two different git ignore files, changes to an existing plugin or adding a new one entirely. I think the real problem here comes from human error and someone forgetting that they have ignored files/folders in a git ignore and not another and accidentally excludes the wrong thing.
Describe alternatives you've considered
Two alternatives come to mind: leave the code as is or build this into a new or existing plugin.