Skip to content

chore(xtask): allow the rdpeudp and rdpemt title scopes - #1628

Merged
Marc-André Moreau (mamoreau-devolutions) merged 1 commit into
Devolutions:masterfrom
lamco-admin:chore/allow-rdpeudp-rdpemt-scopes
Aug 11, 2026
Merged

chore(xtask): allow the rdpeudp and rdpemt title scopes#1628
Marc-André Moreau (mamoreau-devolutions) merged 1 commit into
Devolutions:masterfrom
lamco-admin:chore/allow-rdpeudp-rdpemt-scopes

Conversation

@glamberson

Copy link
Copy Markdown
Contributor

chore(xtask): allow the rdpeudp and rdpemt title scopes

Two entries in CANONICAL_SCOPES, following #1615.

The RDP-UDP transport Marc-André Moreau (@mamoreau-devolutions) asked for on #140 arrives as two
crates, ironrdp-rdpeudp and ironrdp-rdpemt. Neither name is in the list, so
cargo xtask pr check-message rejects the titles of the PRs that add them:
#1626 and #1627 are both red on Check message for exactly this, with
everything else green.

Placed next to rdpeusb, which keeps the protocol extension crates together.

No scope for the tokio adapter

The transport also comes with ironrdp-rdpeudp-tokio, and I have deliberately
not added a scope for it. The list names subsystems rather than crates, which is
why there is no tokio, async, blocking or -native entry either, so
changes to that crate belong under rdpeudp. Say the word if you would rather
have one per crate and I will add it.

Test plan

cargo xtask check fmt/lints/tests/typos/locks

Also checked directly against the titles this unblocks, by feeding each to
cargo xtask pr check-message with a synthetic event file: the two filed PRs
and the three still to come all validate, as does this PR's own title.

The RDP-UDP transport arrives as two crates, `ironrdp-rdpeudp` and
`ironrdp-rdpemt`, and neither name is in the canonical scope list, so
`cargo xtask pr check-message` rejects the titles of the pull requests
that add them.

Placed next to `rdpeusb`, which keeps the protocol extension crates
together.

No scope for the tokio adapter that follows. The list names subsystems
rather than crates, which is why there is no `tokio`, `async` or
`blocking` entry either, so changes to `ironrdp-rdpeudp-tokio` belong
under `rdpeudp`.
@github-actions github-actions Bot added maintainer-required Maintainer review or intervention is required risk/unknown Risk could not be determined automatically; needs maintainer-level scrutiny scope/tooling Build, CI, release, or developer tooling size/XS Size: up to 49 counted lines and 2 files labels Aug 11, 2026
@mamoreau-devolutions
Marc-André Moreau (mamoreau-devolutions) merged commit 8934e4a into Devolutions:master Aug 11, 2026
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintainer-required Maintainer review or intervention is required risk/unknown Risk could not be determined automatically; needs maintainer-level scrutiny scope/tooling Build, CI, release, or developer tooling size/XS Size: up to 49 counted lines and 2 files

Development

Successfully merging this pull request may close these issues.

2 participants