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.
Support editing existing comments instead of overwriting
See original GitHub issueI think it’d be nice (maybe it happens on danger.rb?) for problems that are resolved to be struck out? It makes it hard to track progress and reasons for certain commits.
In this, I’d also like to see some logic to check if the comment if actually a danger comment before overwriting. We use the same bot on a bunch of repos, and it comments about various things in various places. It took me a while to realise that it was still working, but danger was overwriting the comment instead of creating a new one.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi, is there any workaround/hotfix for the same. This feature is really required in our monorepo setup with multiple danger files. Thank you : )
We do support strikeouts in Danger.rb - I’m hesitant to add it in, as it adds a lot of complexity but ended up rarely used when I asked people if they used it.
In rb there is a
--danger_idflag that you can pass, and then it would only update/edit/delete the comment with the same ID. This allowed for multiple Danger’s to comment on the same thread. Would that fix it?