Skip to content

Conversation

@knst
Copy link
Collaborator

@knst knst commented Mar 18, 2024

Issue being fixed or feature implemented

Note: should be this PR either #5949 be merged, not both

Significant part of our code is backported for bitcoin and we should follow bitcoin's codestyle for each particular line for each their implementation.

Without extra tuning and setup this CI doesn't have any value yet spam notification to emails.
Btw, the tool contrib/devtools/clang-diff-format.py still can be called locally to check if any blunder formatting such as 3 spaces.

What was done?

Disabled ci clang-diff-format.yml

How Has This Been Tested?

Let's see this PR runned CIs.

Breaking Changes

N//A

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone

Significant part of our code is backported and we should follow bitcoin's codestyle
Without extra tuning of clang-diff-format it does not have any value
@knst knst added this to the 21 milestone Mar 18, 2024
PastaPastaPasta added a commit that referenced this pull request Apr 2, 2024
adc0e4b fix: apply changes for .clang-format to make it matched with our code style (Konstantin Akimov)
0c884f9 chore: narrow score of clang-diff-format for dash specific files only (Konstantin Akimov)
4bc0e1f chore: intentionally introducing wrong formatting to bip39.cpp to trigger CI (Konstantin Akimov)
2c74ad4 fix: adjust wallet/bip39 accordingly linter comments (Konstantin Akimov)
d3faa85 refactor: use better masks for list of files; add missing bip39.{h,cpp} (Konstantin Akimov)
7788f1d refactor: move list of non backported files o test/util/data/non-backported.txt (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  **Note**: should be this PR either #5942 be merged, not both

  CI clang-format triggers to non-dash files + clang format is differ from out current formatting.

  ## What was done?
  See each commits

  ## How Has This Been Tested?
  See CI result
  To test locally how new style will look, just run this command:
  ```
  diff -u <(cat {coinjoin,governance,llmq,evo,masternode}/*.{h,cpp}) <(clang-format-16 {coinjoin,governance,llmq,evo,masternode}/*.{h,cpp} )
  ```

  ## Breaking Changes
  N/A

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [x] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

Top commit has no ACKs.

Tree-SHA512: d87f30ba78e04f886d7eb2b6b235c20a966bc4438e6428a83ecff5c795d72777516d4270eb9769ffebef9f06e9509acf3c535b4c87b1be6c8a5aef7e2b7efecb
@github-actions
Copy link

github-actions bot commented Apr 2, 2024

This pull request has conflicts, please rebase.

@knst
Copy link
Collaborator Author

knst commented Apr 2, 2024

DNM as #5949 is merged

@knst knst closed this Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant