If a spec PR is merged within few minutes of being opened, the automation will fail to properly trigger
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 115
Description
https://github.com/Azure/azure-rest-api-specs-pr/pull/16788
In this case the comment wasn’t added because the underlying pipeline [failed to check out the repository](https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3439043&view=logs&j=d6a48a56-e996-55ca-2302-c3a9a7be685b&t=b3e85ca8-b38a-5cc1-2420-254eeaae4b0c&l=51). I believe this is because the PR got merged within 3 minutes of being opened, thus deleting the branch that automation was looking for:
> fatal: couldn't find remote ref refs/pull/16788/merge
> ##[error]Git fetch failed with exit code: 128
The PR could get merged so quickly because this is RPSaaSDev branch, so no checks are required, so nothing blocks merge.
Email thread:
> RE: TypeSpec Requirement - 1/25/24
Contributor guide
Assessment
This issue has not been assessed yet.