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
Is your feature request related to a problem? Please describe.
The following works fine:
bundle exec brakeman --only-files foo,bar
The following does not:
bundle exec brakeman --only-files ./foo,./bar
The files are simply skipped.
Describe the solution you'd like
I'd like brakeman to support this kind of notation for files, as a lot of other tools do. This makes automation a lot simpler.
Describe alternatives you've considered
Currently using a shim script in our CI/CD setup to convert all filenames with leading dots to a notation without. This shim script could be discarded if brakeman supported 'leading dot' notation (not sure what the correct term is, relative path prefixed by current dir?).
The text was updated successfully, but these errors were encountered:
Can you explain a little bit more what you are trying to achieve? 🤔
Are you saying Brakeman is running from the root of the Rails application, but some other tooling is passing in paths starting with ./? Even though those paths are in the current directory?
Is your feature request related to a problem? Please describe.
The following works fine:
bundle exec brakeman --only-files foo,bar
The following does not:
bundle exec brakeman --only-files ./foo,./bar
The files are simply skipped.
Describe the solution you'd like
I'd like brakeman to support this kind of notation for files, as a lot of other tools do. This makes automation a lot simpler.
Describe alternatives you've considered
Currently using a shim script in our CI/CD setup to convert all filenames with leading dots to a notation without. This shim script could be discarded if brakeman supported 'leading dot' notation (not sure what the correct term is, relative path prefixed by current dir?).
The text was updated successfully, but these errors were encountered: