-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: remove recursive when downstream and upstream aren't selected #2071
Merged
moshloop
merged 2 commits into
main
from
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
Aug 2, 2024
Merged
chore: remove recursive when downstream and upstream aren't selected #2071
moshloop
merged 2 commits into
main
from
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
Aug 2, 2024
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for goofy-euclid-75956c ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for flanksource-demo-stable ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for clerk-saas-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 9, 2024 07:03
4fdf0be
to
2e57f94
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 9, 2024 09:09
2e57f94
to
84ad283
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 10, 2024 07:14
84ad283
to
0d57f09
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 11, 2024 17:59
0d57f09
to
be2370b
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 12, 2024 09:54
be2370b
to
e960130
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 15, 2024 20:57
e960130
to
1c47a59
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 23, 2024 10:30
1c47a59
to
c14492b
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 25, 2024 18:07
c14492b
to
f1810c7
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 29, 2024 07:53
f1810c7
to
08d9a86
Compare
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 30, 2024 06:56
018c9c1
to
b39d83d
Compare
… use 5 when selected Fixes #2070
mainawycliffe
force-pushed
the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
from
July 31, 2024 14:04
b39d83d
to
1e0991a
Compare
moshloop
deleted the
2070-Config-changes---When-neither-downstreamupstream-selected-default-to-depth-1-and-no-recursive-option
branch
August 2, 2024 06:17
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #2070