microsoft / microsoft/react-native-windows-samples
Website Publish GitHub Action Can Fail When Multiple PRs merged Quickly
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description

See sample here: https://github.com/microsoft/react-native-windows-samples/actions/runs/1048197244
There looks to be a race condition where the various actions race against each other.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sample workflow run linked in the issue and inspect the repository's website publish GitHub Action runs around multiple quick merges. Determine which actions overlap and reproduce the failure if possible. Done means successive merged PRs publish the website reliably without one run interfering with another.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100