Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jul 24, 2023

This is an automatic backport of pull request #529 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* suppress spam in canTransform

* Uncrustify

Signed-off-by: Gonzalo de Pedro <[email protected]>

* Suppress console spam in other calls to canTransform

The user has few options to workaround potential console spam from canTransform.
If we want, it would be better to update the API to optional return the error string.

Signed-off-by: Jacob Perron <[email protected]>

Signed-off-by: Gonzalo de Pedro <[email protected]>
Signed-off-by: Jacob Perron <[email protected]>
Co-authored-by: Grigoriy Lipenko <[email protected]>
Co-authored-by: Jacob Perron <[email protected]>
(cherry picked from commit 8c2aa5a)
@clalancette
Copy link
Contributor

clalancette commented Jul 24, 2023

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@clalancette
Copy link
Contributor

After thinking about this more, I'm not entirely convinced we want to do this in Humble. While it does suppress the spam, it also substantially changes the messages being output by Humble. While that isn't expressly disallowed by our API/ABI policy, I do think it will be a surprise for users. So possibly we shouldn't do this in Humble, I'm not sure. @ahcorde thoughts here?

@clalancette
Copy link
Contributor

After discussing this at the Waffle meeting, we decided that this change in behavior was OK. I'll go ahead and merge this, but @ahcorde if you have another opinion please feel free to leave it here.

@clalancette clalancette merged commit 621be6b into humble Aug 3, 2023
@clalancette clalancette deleted the mergify/bp/humble/pr-529 branch August 3, 2023 17:25
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