Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
@semantic-release/github adds comments to the wrong issues
See original GitHub issueIt looks like @semantic-release/github adds comments to the wrong issues when used in monorepo
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (6 by maintainers)
Top Results From Across the Web
Wrong comments for function addNote · Issue #1634 - GitHub
semantic -release/lib/git.js Lines 321 to 327 in 9635f50 * Get and parse the JSON ... @param {String} ref The Git reference to add...
Read more >Bug: Bot incorrectly comments after release on open ... - GitHub
semantic -release should only add comments to issues that are closed as part of the master commit(s). This is what usually happens. Environment....
Read more >Issues · semantic-release/github
octocat: semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues - Issues · semantic-release/github.
Read more >semantic-release/troubleshooting.md at master - GitHub
When running semantic-release you might encounter the following error: npm ERR! publish Failed PUT 403 npm ERR! code E403 npm ERR!
Read more >Incorrect (duplicate) prerelease version determined even ...
I'm going to move all my packages over to a semantic-release CI/CD trunk-based flow, but most of them already have manually published releases....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks so much for trying it out @travi! That’s good enough for me… just published a new release with the fix!
Our releases are taking longer and longer because it’s adding so many comments to PRs. If someone can point me to the location of what to fix, I can take a stab at it. Maybe wrapping the success plugin?