Skip to content

Conversation

@ayush3797
Copy link
Contributor

@ayush3797 ayush3797 commented Feb 1, 2023

Why make this change?

Fix build warnings: #1156.

Additional change

Failing build if there are warnings.

How was this tested?

Not required.

@ayush3797 ayush3797 self-assigned this Feb 1, 2023
@ayush3797 ayush3797 linked an issue Feb 1, 2023 that may be closed by this pull request
@ayush3797 ayush3797 added this to the Jan2023 milestone Feb 1, 2023
@ayush3797 ayush3797 enabled auto-merge (squash) February 1, 2023 18:37
Copy link
Contributor

@seantleonard seantleonard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

httpstatuscode should be consistent with code sent for other config validation issues. Don't use the authorization forbidden return code

Copy link
Collaborator

@Aniruddh25 Aniruddh25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets fail the build if warnings exist. So, in future, warnings are not overlooked

@ayush3797 ayush3797 merged commit 6ac10dd into main Feb 1, 2023
@ayush3797 ayush3797 deleted the dev/agarwalayush/fixingBuildWarnings branch February 1, 2023 19:31
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.

Fix build warnings

5 participants