Skip to content

[oauth2] Exp claim mandatory (backport to v4.1.x]#16952

Closed
MarcialRosales wants to merge 1 commit into
v4.1.xfrom
exp-claim-mandatory-v4.1.x
Closed

[oauth2] Exp claim mandatory (backport to v4.1.x]#16952
MarcialRosales wants to merge 1 commit into
v4.1.xfrom
exp-claim-mandatory-v4.1.x

Conversation

@MarcialRosales

Copy link
Copy Markdown
Contributor

Proposed Changes

Backport #16878 to v4.1.x

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

@MarcialRosales
MarcialRosales changed the base branch from main to v4.1.x July 15, 2026 15:35
@MarcialRosales MarcialRosales self-assigned this Jul 15, 2026
@Zerpet

Zerpet commented Jul 15, 2026

Copy link
Copy Markdown
Member

@copilot why this PR didn't trigger a workflow run of .github/workflows/test-make.yaml ?

Copilot AI commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@copilot why this PR didn't trigger a workflow run of .github/workflows/test-make.yaml ?

PR #16952 is currently in draft state. GitHub Actions does not trigger pull_request workflows on draft PRs by default — the test-make.yaml workflow's pull_request: trigger (with no types specified) only fires on the default activity types (opened, synchronize, reopened), and GitHub suppresses these events for draft PRs.

You can confirm this by checking the PR's check runs: only Mergify checks are present, with no test-make.yaml run.

To trigger the workflow, mark the PR as Ready for review. That will fire the ready_for_review activity type (and subsequent pushes will trigger synchronize events normally).

Copilot AI requested a review from Zerpet July 15, 2026 15:49
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.

4 participants