René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Handle PullRequest/Action casing in event payloads to detect merged PRs","articleBody":"## Summary\nThe Get-PSModuleSettings action treats merged PRs as abandoned when the event payload uses `PullRequest`/`Action` (PascalCase) keys instead of `pull_request`/`action`.\n\n## Context\nThe GoogleFonts workflow emits event data with `PullRequest` and `Action` properties. When a PR is closed and merged, the evaluated settings show:\n\n- `GITHUB_EVENT_NAME`: pull_request\n- `GITHUB_EVENT_ACTION`: closed\n- `GITHUB_EVENT_PULL_REQUEST_MERGED`: False\n- `isAbandonedPR`: True\n- `isMergedPR`: False\n\nThis causes Publish-Module to run immediately as if the PR was abandoned.\n\n## Expected\nMerged PRs should be detected correctly even when the event payload uses `PullRequest` and `Action` casing.\n\n## Actual\nMerged PRs are treated as abandoned.\n\n## Repro\n1. Trigger the workflow on a merged PR with event payload keys `PullRequest`/`Action` (example payload from GoogleFonts workflow).\n2. Observe the calculated values in Get-PSModuleSettings.\n\n## Proposed fix\nCheck both `action` and `Action`, and both `pull_request` and `PullRequest` when determining PR action and merged status.","author":{"url":"https://github.com/MariusStorhaug","@type":"Person","name":"MariusStorhaug"},"datePublished":"2026-01-17T16:30:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/260/Process-PSModule/issues/260"}