Silence `WARNING: Currently Binder/JupyterHub repositories must be on GitHub, got https://...`
See original GitHub issueDescribe the problem
I’m working on internal documentation, and would like to render notebooks automatically, but there’s no need to launch them with something like Binder.
When I add notebooks, I get the following: WARNING: Currently Binder/JupyterHub repositories must be on GitHub, got https://...
How do I suppress this warning, or indicate that I’d only like to render these notebooks, but not offer a “Launch” option? I’d also like to retain the “Repository” and “Open Issue” buttons, as those can point to our internal sites.
I am compiling with --warningiserror, but I’d like to keep that on to raise an error with other warnings.
Link to your repository or website
No response
Steps to reproduce
Add notebooks that are hosted somewhere other than GitHub.
The version of Python you’re using
No response
Your operating system
No response
Versions of your packages
No response
Additional context
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Publish your book online - Jupyter Book
First, log in to GitHub, then go to the “create a new repository” page: https://github.com/new. Next, give your online repository a name and...
Read more >octokit/rest.js
request { method: 'GET', baseUrl: 'https://api.github.com', headers: { accept: ... Disable a selected repository for GitHub Actions in an organization.
Read more >How can I deal with this Git warning? "Pulling without ...
If the current branch and the remote have diverged, the user needs to specify how to reconcile the divergent branches with --no-ff ...
Read more >Interactive Workflows for C++ with Jupyter | by QuantStack
For this kind of workflow, users of the C++ programming language currently have no choice but to use a heterogeneous set of tools...
Read more >SYSLIB0020 warning - .NET - Microsoft Learn
For more information, see https://github.com/dotnet/runtime/issues/39152. Suppress a warning. If you must use the obsolete APIs, you can ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Essentially the same problem here; I’d like to enable warnings as errors. The person who added this warning may have not been aware that the “Repository” and “Open Issue” buttons work perfectly for a GitLab repository. Would a patch that did nothing but remove the warning be approved?
I’m also looking for a way to avoid this warning, because I need to keep
--warningiserroron.