semantic-release / semantic-release/git
MaxBufferError
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
Hi :)
we are using the @semantic-release/git plugin in a huge monorepo managed by LERNA(https://github.com/lerna/lerna).
With the latest package we added to this monorepo we are encountered a MaxBufferError from your plugin which mainly comes from this "Feature": https://github.com/semantic-release/git/commit/05ab305a380abf6a76aaa81aea0c8fc12fa22782 - or with this configuration on getModifiedFiles() => git -o flag.
Would it be possible to add another configuration target where we could force to use .gitignore or just ignore it, like:
assets: [],
message: "",
gitignore : false
BR
topfblumen
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading getModifiedFiles() and the linked commit that introduced the git -o flag, then trace how the plugin handles large output in a Lerna monorepo. Done means the plugin exposes a documented way to control or bypass the .gitignore behavior without triggering MaxBufferError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100