Skip to content
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

Possibility to pull a single folder #323

Open
joelostblom opened this issue Sep 8, 2023 · 2 comments
Open

Possibility to pull a single folder #323

joelostblom opened this issue Sep 8, 2023 · 2 comments

Comments

@joelostblom
Copy link

Proposed change

We use nbgitpuller to distribute assignments. We don't want students to get all assignments at once but release them week by week. It would be great if nbgitpuller links could be folder specific so that we can give students a link that will always pull down the latest version of only that assignment.

Alternative options

Manually uploading only the latest assignments to a separate github repoi, which is what we currently are doing

Who would use this feature?

Anyone interested in disseminating a partial repo

(Optional): Suggest a solution

Maybe this git technique could be used? https://stackoverflow.com/a/43902478/2166823

@welcome
Copy link

welcome bot commented Sep 8, 2023

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@yuvipanda
Copy link
Contributor

Heya!

Unfortunately partial checkouts are a bit tricky with git, and since nbgitpuller just sits on top of git, I don't think we'll really be able to fully support it.

I think the way to do 'one week at a time' is to have a private repo with all your assignments, do your collaboration there. And then move assignments to the public repo one week at a time, when they're ready to go. This way, users can just re-click the same link to get newest assignment. This is the method we had been using at UC Berkeley for a while.

It might be useful to probably add this to the documentation here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants