semantic-release / semantic-release/commit-analyzer
Is there a way to turn off logs?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
Since every commit being analyzed is logged (with the description as well as the commit message) we sometimes ned up with thousands of lines of logs in our GH Actions consoles when merging together multiple branches... to the point where the browser almost crashes.
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
The issue reports that commit descriptions and messages create excessive logs in GitHub Actions during multi-branch merges. Start by locating the repository's logging behavior and configuration, then determine how logging could be disabled or reduced. Done means large commit analyses no longer flood the Actions console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100