Skip to content

Conversation

@PastaPastaPasta
Copy link
Member

@PastaPastaPasta PastaPastaPasta commented Sep 2, 2021

This will enable us to see if Clang-Format is mad at anything in a PR and will make it easy to tell a PR author what changes to likely do.

This doesn't fail CI, as clang-format is very picky, and we sometimes disagree with it, and I don't think it makes sense at this point to fail. It will only ever output the script output into CI.

See PastaPastaPasta#24

(as a note: if in the future we want to cause this to fail, when format is unhappy, we should modify clang-format-diff.py and add a sys.exit(1) call when there is a problem, and detect that in the action.)

@PastaPastaPasta PastaPastaPasta added this to the 18 milestone Sep 2, 2021
Copy link

@UdjinM6 UdjinM6 left a comment

Choose a reason for hiding this comment

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

utACK

@UdjinM6 UdjinM6 merged commit 20eb136 into dashpay:develop Sep 2, 2021
@PastaPastaPasta PastaPastaPasta deleted the clang-diff-format-action-pr branch September 2, 2021 20:00
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.

2 participants