![]() ![]() Tools like TeamViewer offer similar (and equally dangerous) blanket remote control, but you always know when you’re using it. We’ve also seen how you can use ReviewNB for rich notebook diffs and discussion on Jupyter Notebook pull requests. There’s also a JupyterLab Git extension which helps with many other Git operations. We really need to be able to offer much more fine-grained access controls, so that the (legitimate) user-help scenarios where the “let me become you” usage that we take advantage of all the time can be used, while not exposing these generic gaping holes… We’ve seen how you can use JupyterLab GitPlus to push GitHub commits & create pull requests directly from the Jupyter UI. On hosted systems, we typically think of root as a tiny set of operators who follow very strict protocols- I know root at an HPC center can do anything with my account, but I also trust that they don’t very strongly… Thanks for the great work, this extension is an excellent tool for many users with less experience at the command line!įyundamentally the problem with the admin feature is that it’s a quasi free-for-all “tons of people can be root” with minimal safeguards. But in the long run I’d prefer to have the GUI integrate with the credentials management options directly. ![]() ![]() Git Credential Manager Core for https clones.įor now I’m setting up my SSH agent in a terminal, and using the terminal for push/pulls while taking advantage of the GUI for other operations, and I can also explain that to my students.Installation is pretty straightforward but you do need to provide a GitHub access token for the extension to be able to push commits & open pull request. I am using a Chromebook with Amazon SageMaker to host my Jupyter environment. Here is how I handled it through a Jupyter Terminal. While doing full-on credentials management is certainly outside the scope of this extension, it may be possible to hook into: This is an open source JupyterLab extension that lets you, Push GitHub commits from JupyterLab Create GitHub pull request from JupyterLab Installation. I got here searching for the same solution. In those cases, more advanced users can certainly set up ssh-agent in a terminal, which works (that’s what I do), but they still lose the ability to push from this GUI. While the solution of using a local manager is viable for local installations, it’s much trickier in remotely hosted Hubs, that are typically Linux instances in the cloud (or similar). The issue of easier integration with git credentials management has already been discussed at least in #299 and #348. Is your feature request related to a problem? Please describe. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |