Skip to content

Conversation

@premun
Copy link
Member

@premun premun commented Apr 30, 2025

#4777

Fixes a problem where we were just using the last flown SHA regardless of flow direction. So that can also be the SHA of the last incoming flow while we care about the last ongoing flow.

adamzip
adamzip previously approved these changes Apr 30, 2025
@premun
Copy link
Member Author

premun commented Apr 30, 2025

@premun premun merged commit 4b0818f into dotnet:main Apr 30, 2025
9 checks passed
@premun premun deleted the prvysoky/fix-last-flow-commit-sha branch April 30, 2025 11:56
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.

2 participants