Adds Depth to FetchOptions allowing for shallow cloning

[andersklepaker]

This PR adds Depth to FetchOptions allowing for shallow cloning.

Since I'm new to this repo and it's complexity it's possible i've missed some key information to why this have not been implemented, and if so I'm sorry for not reading up on it prior to submitting this PR.

Resolves #229

[fmargerit]

Hello, what's next for this pull request ?

[andersklepaker]

Hello, what's next for this pull request ?

Someone needs to review and approve it I guess. Not sure if this is something @bording could do?

[andersklepaker]

@amirvenus Do you have write-access and can get this merged?

[goaaats]

Do the unresolved comments block this PR? If the original creator is not around to address them, would it be acceptable for someone else to take over and create a new PR?

[YanisThePie]

so what are the news about this PR?

[dcworldwide]

If practical or required, I'm available to help. Just LMK what I can do.

We are streaming git repo state across a distributed CD/CI system and shallow clones dramatically reduce our bandwidth needs.

[sureshkk]

Is there any updates on this PR?

[karlschriek]

Just to repeat @YanisThePie 's question from earlier. Are any of the comments on the PR actually blocking the merge? I think there may be some arguments that this could go through as it is. If a maintainer could provide feedback and clarify whether adjustments are needed that would be great. If indeed necessary I would be happy to open up a new PR if @andersklepaker is no longer dealing with this.

[andersklepaker]

Thanks for the comments @karlschriek

If a maintainer could provide feedback and clarify whether adjustments are needed that would be great.

Yeah that would be great, and if so happens I'll finish up the work needed for this PR. I did not prioritize investing time here since this repo seems mostly inactive, sadly :(

[IEDAWHI]

Are there any further updates? It would be greatly appreciated if this PR could be merged soon assuming there are no open comments or code changes required.

[YanisThePie]

Please, can someone do something about this forgotten PR?... @amirvenus could you merge this please?

[YanisThePie]

thanks @amirvenus for your approval! Are there still steps to go through before the PR is merge?

[PulsarFX]

@karlschriek I think this PR can now be completed? 🤞

[akirayamamoto]

@bording can you merge this PR?

[kristianbjensen]

Please merge. We have been missing this feature :)

[jhested]

Would also appreciate if this can be merged

[gemolnar]

It would be great if this could be merged.

[YanisThePie]

Is this git repo still maintained?
11 month since the last update, and nobody to merge this PR since months...

[andersklepaker]

This repo is still maintained even tho it is moving very slow. It's a open source project and we can't demand anything. Maintainers are free to do whatever they like, and that is totallly fine. But i'll admit that some kind of feedback from the maintainers would probably not hurt, as a few people have spent time on this PR.

[bording]

Hey everyone. @andersklepaker gets to the heart of things. I'm pretty much the only one left who maintains this repo these days, and I just don't have much free time to devote to it.

This PR does seem to be one that a lot of people are asking for, so I'll try and review it soon.

[DominikKDev]

Thanks a lot @bording. This merge would enable some interesting scenarios, e.g. saving time and space fetching new repositories, so I'm looking forward to the review as well.

[bording]

Thanks for the PR and thanks for your patience!

[YanisThePie]

@bording thanks for your hard work on this amazing project !
Now, What are the steps for the NuGet package to be updated and published with these changes?

[jhested]

@bording Thank you so much for your hard work, I really appreciate it!

[gemolnar]

It was already a great library, and now it's even more useful. Thanks for all your effort!