fix(ci): prevent backport update job from failing on every PR#2898
Closed
Saadnajmi wants to merge 5 commits intomicrosoft:mainfrom
Closed
fix(ci): prevent backport update job from failing on every PR#2898Saadnajmi wants to merge 5 commits intomicrosoft:mainfrom
Saadnajmi wants to merge 5 commits intomicrosoft:mainfrom
Conversation
Implements onAuxClick following the same pattern as onDoubleClick, wired end-to-end from native rightMouseUp: through C++ event emitters to JS. Also adds a `button` field to MouseEvent and filters non-primary button clicks from triggering onPress in Pressability. Inspired by microsoft/react-native-windows#15920. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Port the shared changes from facebook#56298: - Add onAuxClick/onAuxClickCapture to TouchEventEmitter (shared C++) - Add AuxClick/AuxClickCapture to ViewEvents in primitives.h - Add prop conversions in propsConversions.h - Register topAuxClick as a bubbling event in BaseViewConfig.ios.js - Add dispatch logic in RCTSurfacePointerHandler.mm (iOS path) - Type onAuxClick as PointerEvent in PointerEventProps (Flow + TS) Remove redundant macOS-specific JS registrations since macOS now inherits the bubbling event from the iOS base config. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Match react-native-windows approach: add _isDefaultPressButton() helper and use it in all three press paths (onClick, LONG_PRESS_DETECTED, and RESPONDER_RELEASE). The button property is already forwarded from native macOS touch events via BaseTouch. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add MouseClickEventsExample to ViewExample.js with both a plain View and a Pressable target to verify onAuxClick fires and onPress does not on right-click - Document onAuxClick in docsite view-events.md with event data spec and usage example - Add button property to onDoubleClick event data docs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Move the GitHub App token generation step after the backport PR lookup in the update-backport job. The lookup now uses the default github.token (which always works) and all subsequent steps are skipped when no backport PRs exist. This prevents the job from failing on every PR push due to token generation errors when there's nothing to update. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
update-backportjob so the backport PR lookup runs first using the defaultgithub.tokenfound == 'true', so they're skipped when no backport PRs existTest plan
main— the "Update backport PRs" job should pass (with steps skipped)/backport <branch>on a PR — the "Create backport" job should still work as before🤖 Generated with Claude Code