Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

formatters/ruby:chore - removing unnecessary error messages #1024

Merged
merged 1 commit into from
Mar 10, 2022

Conversation

nathanmartinszup
Copy link
Contributor

@nathanmartinszup nathanmartinszup commented Mar 10, 2022

Previously if the project had ruby between programming languages but is
not a ruby on rails project or does not have a Gemfile.lock an error
would be reported for each scenario.

This pull request changes these error messages introduced in commits
cd839ef and 9245d7d to be considered just warnings, as there is no
need to point them out as errors, since it is only intended to
inform the user.

Signed-off-by: Nathan Martins nathan.martins@zup.com.br

- What I did

- How to verify it

- Description for the changelog

@nathanmartinszup nathanmartinszup force-pushed the chore/bundler-brakeman-warnings branch from deb3ce5 to be3f158 Compare March 10, 2022 14:27
Previously if the project had ruby between programming languages but is
not a ruby on rails project or does not have a Gemfile.lock an error
would be reported for each scenario.

This pull request changes these error messages introduced in commits
cd839ef and 9245d7d to be considered just warnings, as there is no
need to point them out as errors, since it is only intended to
inform the user.

Signed-off-by: Nathan Martins <nathan.martins@zup.com.br>
@matheusalcantarazup matheusalcantarazup merged commit 358fd4a into main Mar 10, 2022
@matheusalcantarazup matheusalcantarazup deleted the chore/bundler-brakeman-warnings branch March 10, 2022 16:01
matheusalcantarazup pushed a commit that referenced this pull request Mar 10, 2022
Previously if the project had ruby between programming languages but is
not a ruby on rails project or does not have a Gemfile.lock an error
would be reported for each scenario.

This pull request changes these error messages introduced in commits
cd839ef and 9245d7d to be considered just warnings, as there is no
need to point them out as errors, since it is only intended to
inform the user.

Signed-off-by: Nathan Martins <nathan.martins@zup.com.br>
(cherry picked from commit 358fd4a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants