We've been successfully using SonarLint https://www.sonarlint.org/ for pre-commit static analysis. Every developer is required to run it before submitting his/her changes for review. You can bind the

#security #clm

+1 on being able to scan a commit rather than having to go through whole merge process - if that is possible, it would allow a committer to work these issues without having to wait for Non-author code

#security #clm

Issue closed for myself - keep as-is for the wiki security lockdown Had a discussion with Roger just now that jogged my brain (I jogged in the forest a couple days ago) - and I completely forgot about

#security #clm

Catherine, The situation on the ground is more fluid - we may get someone to fix a CLM issue for a couple hours - then they get assigned to other work. All of us are security experts as some point. A

#security #clm

Good morning Michael, Manoop, As previously discussed, we are not authorized to copy/paste the complete CLM report to the ONAP wiki. What you can or can’t do - has been previously documented here: htt

#clm #security

+1 The Portal team also in similar situation. The two security experts in our team are not PTL or committers, so they cannot access the CLM reports leading to delay in analyzing the impact and action

#clm #security

Hi, I was wondering if we can get the security rules relaxed – currently I would need to copy/paste wiki content for other members of the team doing the CLM work. Thank you /michael

#clm #security

Team, Hi, I have a request on behalf of my team and likely others. The CLM security pages are locked down too tightly – I would like other members of the team – in particular Prudence Au (my co-PTL al

#clm #security