Skip to content

chore: ask for just pre-push in PR template - #386

Open
vadim-anfv wants to merge 1 commit into
bitcoindevkit:masterfrom
vadim-anfv:chore/pr-template
Open

vadim-anfv wants to merge 1 commit into
bitcoindevkit:masterfrom
vadim-anfv:chore/pr-template

Conversation

@vadim-anfv

@vadim-anfv vadim-anfv commented Nov 12, 2026 •

Copy link
Copy Markdown
Collaborator

Description

cargo fmt and cargo clippy miss the feature-gated failures that CI then reports. just pre-push also runs the tests and clippy with -D warnings on both feature sets.

Notes to the reviewers

That cargo line in checks below comes from the current template, not the new one.
And yes, I did run the commands.

Checklists

All Submissions:

  • I've signed all my commits
  • I followed the contribution guidelines
  • I ran cargo fmt and cargo clippy before committing

@codecov

codecov Bot commented Nov 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.51%. Comparing base (5558555) to head (dce8f4b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #386      +/-   ##
==========================================
- Coverage   60.00%   59.51%   -0.50%     
==========================================
  Files          25       25              
  Lines        4736     4552     -184     
==========================================
- Hits         2842     2709     -133     
+ Misses       1894     1843      -51     
Flag Coverage Δ
rust 59.51% <ø> (-0.50%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tvpeter tvpeter left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

ACK dce8f4b

vadim-anfv added a commit that referenced this pull request Nov 14, 2026
eb9536d ci: make tracing optional, drop cli-table (Vadim Anufriev)
22a01a3 refactor(payjoin): return session history as JSON (Vadim Anufriev)

Pull request description:

  ### Description

  The `--no-default-features` build and clippy jobs are red on every open PR, including Markdown-only ones (#386, #387). `cli-table`, `tracing` and `tracing-subscriber` are unused there, and recent cargo flags that ([`unused_dependencies`](https://doc.rust-lang.org/cargo/reference/lints.html#unused_dependencies), warn by default) while the workflow passes `build-warnings: deny`.

  `cli-table` is dropped entirely, as @tvpeter suggested: its last user, the payjoin session history, now returns JSON like the rest of the module.

  `payjoin history` on `master`:

  ```
  +------------+-----------------+---------------------+-------------------------------+
  | Session ID | Sender/Receiver | Completed At        | Status                        |
  +------------+-----------------+---------------------+-------------------------------+
  | 1          | Receiver        | Not Completed       | Waiting for original proposal |
  +------------+-----------------+---------------------+-------------------------------+
  | 2          | Receiver        | 2026-11-13 17:50:42 | Session cancelled             |
  +------------+-----------------+---------------------+-------------------------------+
  ```

  and on this branch:

  ```json
  {
    "sessions": [
      {
        "id": "1",
        "role": "Receiver",
        "status": "Waiting for original proposal",
        "completed_at": null
      },
      {
        "id": "2",
        "role": "Receiver",
        "status": "Session cancelled",
        "completed_at": "2026-11-13 18:34:22"
      }
    ]
  }
  ```

  ### Notes to the reviewers

  An active session now reports `"completed_at": null` instead of the string `Not Completed`.

  `tracing` is on `cbf` explicitly, although `cbf` already implies `_payjoin-dependencies`, so cbf logging does not depend on a payjoin-internal feature.

  `just pre-push` misses this: the lint is cargo's, not rustc's, so `-D warnings` after `--` does not apply. To reproduce: `cargo build --no-default-features --config 'build.warnings="deny"'`.

  The `SessionHistory` wrapper exists to keep the field order: serializing it directly preserves declaration order, while `json!` would sort the keys alphabetically.

  ### Checklists

  #### All Submissions:

  * [x] I've signed all my commits
  * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk-cli/blob/master/CONTRIBUTING.md)
  * [x] I ran `cargo fmt` and `cargo clippy` before committing

ACKs for top commit:
  tvpeter:
    ACK eb9536d

Tree-SHA512: 556923b5466720ea21dca4a7d4a5798e48cf2b317db0fbab68b3b94e20d6b822edab3d57c2a12e97f4b5c90e52ea727ba3770eb952da30423a26958d69a6e5d5
@vadim-anfv

Copy link
Copy Markdown
Collaborator Author

@tvpeter rebased onto master after #389 for green CI. Needs an ACK on the new head.

@vadim-anfv
vadim-anfv requested a review from tvpeter November 14, 2026 06:11

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

2 participants