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.

Sign up for GitHub

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

Jump to bottom

Better clang-format diagnostics from Travis CI #177

Open
leha-bot opened this issue Aug 5, 2018 · 0 comments
Open

Better clang-format diagnostics from Travis CI #177

leha-bot opened this issue Aug 5, 2018 · 0 comments
Labels
category:Infrastructure Related to build tools, automation category:Question This is an inquiry for information, not a change request

Comments

@leha-bot
Copy link
Member

leha-bot commented Aug 5, 2018

Right now there is an obscure output if commit violates the Procrust clang-format rules.
I recommend to improve the diagnostics log (e.g. write a diff with formatted and unformatted code, or whatever).

Discuss.
@leha-bot leha-bot added category:Question This is an inquiry for information, not a change request category:Infrastructure Related to build tools, automation labels Aug 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category:Infrastructure Related to build tools, automation category:Question This is an inquiry for information, not a change request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leha-bot