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
Our microsoft/STL repo contains llvm-project as a submodule (to use libc++'s test coverage), and Microsoft's credential scanners are complaining about the password on line 50. (I'm not sure if the passcode on line 60 is problematic for the scanner, but it's possible. I'm also not sure whether it's specifically the word "password" that's being detected, or the structure of the gibberish characters.)
Silencing this alert or obtaining an exemption are really difficult for us (even though it's not a Microsoft credential at all). Could you update this markdown file to avoid having passwords/passcodes for these meetings? Moving them to your linked Google Doc would be fine for us.
The text was updated successfully, but these errors were encountered:
…tation
The passwords are moved to the Google Doc containing the agenda and minutes
for the calls. A note has been added mentioning where to find the meeting ID's
and passwords.
Fixesllvm#96121
llvm#98161)
…tation
The passwords are moved to the Google Doc containing the agenda and
minutes for the calls. A note has been added mentioning where to find
the meeting ID's and passwords.
Fixesllvm#96121
#81147 by @tarunprabhu added:
llvm-project/flang/docs/GettingInvolved.md
Line 50 in 89e8e63
llvm-project/flang/docs/GettingInvolved.md
Line 60 in 89e8e63
Our microsoft/STL repo contains llvm-project as a submodule (to use libc++'s test coverage), and Microsoft's credential scanners are complaining about the password on line 50. (I'm not sure if the passcode on line 60 is problematic for the scanner, but it's possible. I'm also not sure whether it's specifically the word "password" that's being detected, or the structure of the gibberish characters.)
Silencing this alert or obtaining an exemption are really difficult for us (even though it's not a Microsoft credential at all). Could you update this markdown file to avoid having passwords/passcodes for these meetings? Moving them to your linked Google Doc would be fine for us.
The text was updated successfully, but these errors were encountered: