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

archive issue trackers #1920

Open
njr2128 opened this issue Oct 22, 2020 · 4 comments
Open

archive issue trackers #1920

njr2128 opened this issue Oct 22, 2020 · 4 comments
Assignees
Labels
qc quality control

Comments

@njr2128
Copy link
Member

njr2128 commented Oct 22, 2020

using Github's API, archive all issues

@njr2128
Copy link
Member Author

njr2128 commented Nov 9, 2020

simple recursive crawl of html:
wget -r -np -k https://github.com/cu-mkp/m-k-manuscript-data/issues/

@njr2128
Copy link
Member Author

njr2128 commented Nov 9, 2020

Another tool for a similar strategy (just local harvest of site): http://www.httrack.com/

@njr2128
Copy link
Member Author

njr2128 commented Nov 9, 2020

from @tcatapano - another idea:
use json output from the github rest api to serve as input to Jekyll to generate a static site

  • for example, each issue json record is converted to md document with associated metadata in the yaml header
  • should each comment in an issue be part of the md issue page or be its own page and linked to? ¯\_(ツ)_/¯

@gschare
Copy link
Contributor

gschare commented Nov 14, 2020

Here's a gist of the Python code needed to get the issues.
Currently I'm just grabbing all the information for the issues and comments.
The content of each issue and comment is given in Markdown, so it would definitely work to generate a static site with Jekyll.

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

No branches or pull requests

2 participants