Open
Conversation
bkhouri
force-pushed
the
t/main/pr_dependency-check
branch
from
28da7c7 to
6f41ed3
Compare
Contributor
Author
|
Closing this PR as there is an existing GitHub Action: https://github.com/gregsdennis/dependencies-action |
bkhouri
force-pushed
the
t/main/pr_dependency-check
branch
from
6f41ed3 to
3280684
Compare
shahmishal
reviewed
Mar 10, 2026
shahmishal
reviewed
Mar 10, 2026
shahmishal
reviewed
Mar 10, 2026
shahmishal
reviewed
Mar 10, 2026
bkhouri
force-pushed
the
t/main/pr_dependency-check
branch
4 times, most recently
from
b4ce1a7 to
875a34f
Compare
bkhouri
force-pushed
the
t/main/pr_dependency-check
branch
from
875a34f to
71643ce
Compare
bkhouri
force-pushed
the
t/main/pr_dependency-check
branch
from
bfc25a8 to
b88cd06
Compare
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
2 participants
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.
While working on a project, I tend to build one PR on top of another. And although The later PR can be merged and include all the child PR, it's not ideal as it can lead to the "parent" PR being closed without having any references to approval - as the approvals were given in a child PR.
Sometimes SwiftPM PR's are depend on a change in https://github.com/swiftlang/swift-build, or even changes in https://github.com/swiftlang/swift
Here's are examples of the two scenarios: