You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #36 implemented a gh-action to compile a list of open documentation issues across Jupyter sub-projects, the output was being saved in a CSV file in the main branch. Such behaviour (ie, autonomous creation of commits to the main branch) was changed in PR #39.
PR #39 modified the location of that workflow's output: now, the workflow was creating an HTML table in gh-pages branch. This would keep the main branch clear from bot-created commits, plus we would be able to see the list of issues through an html page with features such as filtering and sorting.
There is, though, a redirection from jupyter.github.io to jupyter.org which renders the HTML table (in GitHub pages) inaccessible. Meaning that we should find another venue to such table of issues.
The text was updated successfully, but these errors were encountered:
The way to go is to go back toCSV file (in a different branch than main), and use the GH's Flat data little project, https://github.com/githubocto/flat. The Flat framework is composed by a viewer that we can to have a nice view of flat files -- eg, CSV files -- in a GH repository.
PR #36 implemented a gh-action to compile a list of open
documentation
issues across Jupyter sub-projects, the output was being saved in a CSV file in the main branch. Such behaviour (ie, autonomous creation of commits to the main branch) was changed in PR #39.PR #39 modified the location of that workflow's output: now, the workflow was creating an HTML table in
gh-pages
branch. This would keep themain
branch clear from bot-created commits, plus we would be able to see the list of issues through an html page with features such as filtering and sorting.There is, though, a redirection from
jupyter.github.io
tojupyter.org
which renders the HTML table (in GitHub pages) inaccessible. Meaning that we should find another venue to such table of issues.The text was updated successfully, but these errors were encountered: