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

Provide a pull-only mode that completely overwrites local files #998

Closed
orome opened this issue Aug 3, 2021 · 2 comments · Fixed by #1087
Closed

Provide a pull-only mode that completely overwrites local files #998

orome opened this issue Aug 3, 2021 · 2 comments · Fixed by #1087

Comments

@orome
Copy link
Contributor

orome commented Aug 3, 2021

Is your feature request related to a problem? Please describe.

I would like to use jupyterlab-git in the context of a shared project (e.g., though Binder), where contributions from users are not supported, and where any pulls should completely overwrite (and prune) local files. I know there are limited existing solutions for similar scenarios, but they create a layer (or more) of abstraction above Git, that results in the loss of information (e.g. jupyterlab-git effectively provides notification of remote changes).

Describe the solution you'd like

It would be great of jupyterlab-git provided settings that

  1. prevented any pushing, and
  2. where all pulls completely overwrote (and pruned) local files

while still providing all of the other file viewing, diffing, and other features it supports

Describe alternatives you've considered

Other solutions like nbgitpuller are very limited.

@meeseeksmachine
Copy link

This issue has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/what-is-installed-by-default-with-binder/10217/11

@fcollonval
Copy link
Member

Nice suggestion @orome

If you want I can provide pointers to help you start a PR for this one.

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

Successfully merging a pull request may close this issue.

3 participants