You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. We are using Bandit on a fairly large code base and have a very big baseline for it. When a new version comes out, I often have to regenerate the baseline, and even if I want to add just one more issue found, the diff to the baseline gets huge because every "more_info" link is updated to the new version. This makes it pretty hard to review.
Is it possible to e.g. disable that key, or to always use "latest" rather than the specific version? Or is there another suggested way to handle this?
I wouldn't mind the specific bandit version used to appear one time (like "generated_at" for example), but I would like to omit it from each issue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi. We are using Bandit on a fairly large code base and have a very big baseline for it. When a new version comes out, I often have to regenerate the baseline, and even if I want to add just one more issue found, the diff to the baseline gets huge because every "more_info" link is updated to the new version. This makes it pretty hard to review.
Is it possible to e.g. disable that key, or to always use "latest" rather than the specific version? Or is there another suggested way to handle this?
I wouldn't mind the specific bandit version used to appear one time (like "generated_at" for example), but I would like to omit it from each issue.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions