[FEATURE] Add Issue Ticket Discussion Behaviours to RSE Personas Methods

[FlicAnderson]

Brief task description: - What needs to be done for this task/feature

Issue Ticket Discussion Behaviours:

• Write discussions interactions gathering API code [sprint1]
• Integrate to workflow [sprint1]
• Combine with other interactions data [sprint1]
• Collect for Set1 repos [sprint1]
• Collect for Set2 repos [sprint2]
• Collect for Russell et al repos [sprint2]

Does it relate to any other work / issues: - No | Yes (details...)

Why is it needed? - Justification details for why this will be time well-spent and how it progresses my project work.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

How should it be done? - Give a rough idea here, follow up with more details in further tickets as needed.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

How will I know when it's done? - When should this task/feature be considered 'finished'?
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Any other details of relevance? - Extra info, relevant links, prioritisation discussion etc.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

[FlicAnderson]

Created ''get_all_issue_ticket_discussions.py" script.

[FlicAnderson]

Considered whether to include these:

PR discussions comments, or 'discussion comments on a PR':

API endpoint repo_name/issues/comments

These include 'non-review' comments on PR (id: 3135853937) and are found through issues/comments endpoint; but probably should be INCLUDED for PR code review purposes.

Personally: I believe these SHOULD be counted as PR CRs (pull request code review interactions), even though they show up on the issues endpoints, because they involve interacting with pull requests which are already established.

[FlicAnderson]

[FlicAnderson]

Some difficulty deciding how to separate the PR-CR #97 and discussions code, as there's a lot of overlap in the workflow.

Currently can obtain the issue ticket discussions, and separate off the PR discussions (currently not handled inget_all_PR_code_reviews.py but should be somehow?).

Still TODO:
Handling the output data and linking into the rest of the interactions dataset.
NOTE: this could be done DURING a data-grab run, as the data is coming in, with a smaller set of data.

[FlicAnderson]

Next steps involve creating a script step similar to pre-analysis_data_issues_prep.py to collate/combine the processed-issues equivalent for discussions.

[FlicAnderson]

Issue Ticket discussions update:

• DONE running on long list of test repos for discussions
• process .jsons for sub-review and main-review into .csv and df them;
• integrate df'd PR-CR data for PR-discussions; sub-review; main-review content as 1 interaction type.
• run data collection for ALL Set1 repos
• integrate with rest of interactions data subsequently.

[FlicAnderson]

Checks:

• all files exist as expected for the test repos
• all files have legit file sizes
• files contents' can be read in for each repo
• read-in content seems legit in terms of N items matches logger output summary numbers

[FlicAnderson]

discussions
discussions
processing repo 0 of 16
processing repo: KislakCenter/VisColl.
INFO:There are 6 items across all pages.
INFO:Checking whether repo KislakCenter/VisColl has issues enabled.
Attempting to find issues content for repo: KislakCenter/VisColl
INFO:Running run_all_issues() to get all issues data for repo KislakCenter/VisColl.
INFO:Checking whether issue tickets data for repo KislakCenter/VisColl for today's date already exists at path ../../data/all-issues_KislakCenter-VisColl_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is KislakCenter/VisColl. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo KislakCenter/VisColl, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 10
INFO:10 issues returned from repo KislakCenter/VisColl at ../../data/all-issues_KislakCenter-VisColl_2025-11-13.json.
INFO:There are 10 issues for repo KislakCenter/VisColl.
INFO:Saved out issues data to ../../data/processed-issues_KislakCenter-VisColl_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 6 discussions for repo KislakCenter/VisColl.
INFO:There are 6 non-PR type issue ticket discussions for repo KislakCenter/VisColl.
INFO:There are 0 PR type issue ticket discussions for repo KislakCenter/VisColl.
INFO:Saved out ALL discussions data for repo KislakCenter/VisColl to ../../data/all-discussions_KislakCenter-VisColl_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo KislakCenter/VisColl to ../../data/non-PR-issue-discussions_KislakCenter-VisColl_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo KislakCenter/VisColl to ../../data/PR-issue-discussions_KislakCenter-VisColl_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 1 of 16
processing repo: LABSN/expyfun.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=7.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=8.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=9.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=10.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=11.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=12.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=13.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=14.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=15.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=16.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=17.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=18.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=19.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=20.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=21.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=22.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=23.
INFO:getting json via request url https://api.github.com/repositories/11614571/issues/comments?per_page=100&page=24.
INFO:There are 2387 items across all pages.
INFO:Checking whether repo LABSN/expyfun has issues enabled.
Attempting to find issues content for repo: LABSN/expyfun
INFO:Running run_all_issues() to get all issues data for repo LABSN/expyfun.
INFO:Checking whether issue tickets data for repo LABSN/expyfun for today's date already exists at path ../../data/all-issues_LABSN-expyfun_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is LABSN/expyfun. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo LABSN/expyfun, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo LABSN/expyfun, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo LABSN/expyfun, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 300
INFO:>> Running issue grab for repo LABSN/expyfun, in page 4.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 400
INFO:>> Running issue grab for repo LABSN/expyfun, in page 5.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 500
INFO:>> Running issue grab for repo LABSN/expyfun, in page 6.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 541
INFO:541 issues returned from repo LABSN/expyfun at ../../data/all-issues_LABSN-expyfun_2025-11-13.json.
INFO:There are 541 issues for repo LABSN/expyfun.
INFO:Saved out issues data to ../../data/processed-issues_LABSN-expyfun_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 2387 discussions for repo LABSN/expyfun.
INFO:There are 680 non-PR type issue ticket discussions for repo LABSN/expyfun.
INFO:There are 1707 PR type issue ticket discussions for repo LABSN/expyfun.
INFO:Saved out ALL discussions data for repo LABSN/expyfun to ../../data/all-discussions_LABSN-expyfun_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo LABSN/expyfun to ../../data/non-PR-issue-discussions_LABSN-expyfun_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
INFO:Saved out pull-request discussions data for repo LABSN/expyfun to ../../data/PR-issue-discussions_LABSN-expyfun_2025-11-13.csv.
processing repo 2 of 16
processing repo: SyneRBI/SIRF-SuperBuild.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=7.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=8.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=9.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=10.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=11.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=12.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=13.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=14.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=15.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=16.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=17.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=18.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=19.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=20.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=21.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=22.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=23.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=24.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=25.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=26.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=27.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=28.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=29.
INFO:getting json via request url https://api.github.com/repositories/79476388/issues/comments?per_page=100&page=30.
INFO:There are 2987 items across all pages.
INFO:Checking whether repo SyneRBI/SIRF-SuperBuild has issues enabled.
Attempting to find issues content for repo: SyneRBI/SIRF-SuperBuild
INFO:Running run_all_issues() to get all issues data for repo SyneRBI/SIRF-SuperBuild.
INFO:Checking whether issue tickets data for repo SyneRBI/SIRF-SuperBuild for today's date already exists at path ../../data/all-issues_SyneRBI-SIRF-SuperBuild_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is SyneRBI/SIRF-SuperBuild. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 300
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 4.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 400
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 5.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 500
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 6.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 600
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 7.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 700
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 8.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 800
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 9.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 900
INFO:>> Running issue grab for repo SyneRBI/SIRF-SuperBuild, in page 10.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 961
INFO:961 issues returned from repo SyneRBI/SIRF-SuperBuild at ../../data/all-issues_SyneRBI-SIRF-SuperBuild_2025-11-13.json.
INFO:There are 961 issues for repo SyneRBI/SIRF-SuperBuild.
INFO:Saved out issues data to ../../data/processed-issues_SyneRBI-SIRF-SuperBuild_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 2987 discussions for repo SyneRBI/SIRF-SuperBuild.
INFO:There are 1612 non-PR type issue ticket discussions for repo SyneRBI/SIRF-SuperBuild.
INFO:There are 1375 PR type issue ticket discussions for repo SyneRBI/SIRF-SuperBuild.
INFO:Saved out ALL discussions data for repo SyneRBI/SIRF-SuperBuild to ../../data/all-discussions_SyneRBI-SIRF-SuperBuild_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
INFO:Saved out non-pull-request discussions data for repo SyneRBI/SIRF-SuperBuild to ../../data/non-PR-issue-discussions_SyneRBI-SIRF-SuperBuild_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo SyneRBI/SIRF-SuperBuild to ../../data/PR-issue-discussions_SyneRBI-SIRF-SuperBuild_2025-11-13.csv.
processing repo 3 of 16
processing repo: avaframe/AvaFrame.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=7.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=8.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=9.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=10.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=11.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=12.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=13.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=14.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=15.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=16.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=17.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=18.
INFO:getting json via request url https://api.github.com/repositories/281922740/issues/comments?per_page=100&page=19.
INFO:There are 1900 items across all pages.
INFO:Checking whether repo avaframe/AvaFrame has issues enabled.
Attempting to find issues content for repo: avaframe/AvaFrame
INFO:Running run_all_issues() to get all issues data for repo avaframe/AvaFrame.
INFO:Checking whether issue tickets data for repo avaframe/AvaFrame for today's date already exists at path ../../data/all-issues_avaframe-AvaFrame_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is avaframe/AvaFrame. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 300
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 4.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 400
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 5.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 500
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 6.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 600
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 7.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 700
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 8.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 800
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 9.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 900
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 10.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 1000
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 11.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 1100
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 12.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 1200
INFO:>> Running issue grab for repo avaframe/AvaFrame, in page 13.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 1207
INFO:1207 issues returned from repo avaframe/AvaFrame at ../../data/all-issues_avaframe-AvaFrame_2025-11-13.json.
INFO:There are 1207 issues for repo avaframe/AvaFrame.
INFO:Saved out issues data to ../../data/processed-issues_avaframe-AvaFrame_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 1900 discussions for repo avaframe/AvaFrame.
INFO:There are 359 non-PR type issue ticket discussions for repo avaframe/AvaFrame.
INFO:There are 1541 PR type issue ticket discussions for repo avaframe/AvaFrame.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
INFO:Saved out ALL discussions data for repo avaframe/AvaFrame to ../../data/all-discussions_avaframe-AvaFrame_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo avaframe/AvaFrame to ../../data/non-PR-issue-discussions_avaframe-AvaFrame_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo avaframe/AvaFrame to ../../data/PR-issue-discussions_avaframe-AvaFrame_2025-11-13.csv.
processing repo 4 of 16
processing repo: cookiejar/cookietemple.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=7.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=8.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=9.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=10.
INFO:getting json via request url https://api.github.com/repositories/202421008/issues/comments?per_page=100&page=11.
INFO:There are 1031 items across all pages.
INFO:Checking whether repo cookiejar/cookietemple has issues enabled.
Attempting to find issues content for repo: cookiejar/cookietemple
INFO:Running run_all_issues() to get all issues data for repo cookiejar/cookietemple.
INFO:Checking whether issue tickets data for repo cookiejar/cookietemple for today's date already exists at path ../../data/all-issues_cookiejar-cookietemple_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is cookiejar/cookietemple. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 300
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 4.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 400
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 5.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 500
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 6.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 600
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 7.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 700
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 8.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 800
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 9.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 900
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 10.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 1000
INFO:>> Running issue grab for repo cookiejar/cookietemple, in page 11.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 1085
INFO:1085 issues returned from repo cookiejar/cookietemple at ../../data/all-issues_cookiejar-cookietemple_2025-11-13.json.
INFO:There are 1085 issues for repo cookiejar/cookietemple.
INFO:Saved out issues data to ../../data/processed-issues_cookiejar-cookietemple_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 1031 discussions for repo cookiejar/cookietemple.
INFO:There are 597 non-PR type issue ticket discussions for repo cookiejar/cookietemple.
INFO:There are 434 PR type issue ticket discussions for repo cookiejar/cookietemple.
INFO:Saved out ALL discussions data for repo cookiejar/cookietemple to ../../data/all-discussions_cookiejar-cookietemple_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo cookiejar/cookietemple to ../../data/non-PR-issue-discussions_cookiejar-cookietemple_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo cookiejar/cookietemple to ../../data/PR-issue-discussions_cookiejar-cookietemple_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 5 of 16
processing repo: genomeannotation/GAG.
INFO:getting json via request url https://api.github.com/repositories/11934756/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/11934756/issues/comments?per_page=100&page=3.
INFO:There are 245 items across all pages.
INFO:Checking whether repo genomeannotation/GAG has issues enabled.
Attempting to find issues content for repo: genomeannotation/GAG
INFO:Running run_all_issues() to get all issues data for repo genomeannotation/GAG.
INFO:Checking whether issue tickets data for repo genomeannotation/GAG for today's date already exists at path ../../data/all-issues_genomeannotation-GAG_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is genomeannotation/GAG. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo genomeannotation/GAG, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo genomeannotation/GAG, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 198
INFO:198 issues returned from repo genomeannotation/GAG at ../../data/all-issues_genomeannotation-GAG_2025-11-13.json.
INFO:There are 198 issues for repo genomeannotation/GAG.
INFO:Saved out issues data to ../../data/processed-issues_genomeannotation-GAG_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 245 discussions for repo genomeannotation/GAG.
INFO:There are 242 non-PR type issue ticket discussions for repo genomeannotation/GAG.
INFO:There are 3 PR type issue ticket discussions for repo genomeannotation/GAG.
INFO:Saved out ALL discussions data for repo genomeannotation/GAG to ../../data/all-discussions_genomeannotation-GAG_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo genomeannotation/GAG to ../../data/non-PR-issue-discussions_genomeannotation-GAG_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo genomeannotation/GAG to ../../data/PR-issue-discussions_genomeannotation-GAG_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 6 of 16
processing repo: gher-uliege/DIVAnd.jl.
INFO:getting json via request url https://api.github.com/repositories/79277337/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/79277337/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/79277337/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/79277337/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/79277337/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/79277337/issues/comments?per_page=100&page=7.
INFO:There are 689 items across all pages.
INFO:Checking whether repo gher-uliege/DIVAnd.jl has issues enabled.
Attempting to find issues content for repo: gher-uliege/DIVAnd.jl
INFO:Running run_all_issues() to get all issues data for repo gher-uliege/DIVAnd.jl.
INFO:Checking whether issue tickets data for repo gher-uliege/DIVAnd.jl for today's date already exists at path ../../data/all-issues_gher-uliege-DIVAnd.jl_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is gher-uliege/DIVAnd.jl. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo gher-uliege/DIVAnd.jl, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo gher-uliege/DIVAnd.jl, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 156
INFO:156 issues returned from repo gher-uliege/DIVAnd.jl at ../../data/all-issues_gher-uliege-DIVAnd.jl_2025-11-13.json.
INFO:There are 156 issues for repo gher-uliege/DIVAnd.jl.
INFO:Saved out issues data to ../../data/processed-issues_gher-uliege-DIVAnd.jl_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 689 discussions for repo gher-uliege/DIVAnd.jl.
INFO:There are 614 non-PR type issue ticket discussions for repo gher-uliege/DIVAnd.jl.
INFO:There are 75 PR type issue ticket discussions for repo gher-uliege/DIVAnd.jl.
INFO:Saved out ALL discussions data for repo gher-uliege/DIVAnd.jl to ../../data/all-discussions_gher-uliege-DIVAnd.jl_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo gher-uliege/DIVAnd.jl to ../../data/non-PR-issue-discussions_gher-uliege-DIVAnd.jl_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo gher-uliege/DIVAnd.jl to ../../data/PR-issue-discussions_gher-uliege-DIVAnd.jl_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 7 of 16
processing repo: gwdetchar/gwdetchar.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=7.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=8.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=9.
INFO:getting json via request url https://api.github.com/repositories/36960054/issues/comments?per_page=100&page=10.
INFO:There are 931 items across all pages.
INFO:Checking whether repo gwdetchar/gwdetchar has issues enabled.
Attempting to find issues content for repo: gwdetchar/gwdetchar
INFO:Running run_all_issues() to get all issues data for repo gwdetchar/gwdetchar.
INFO:Checking whether issue tickets data for repo gwdetchar/gwdetchar for today's date already exists at path ../../data/all-issues_gwdetchar-gwdetchar_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is gwdetchar/gwdetchar. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo gwdetchar/gwdetchar, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo gwdetchar/gwdetchar, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo gwdetchar/gwdetchar, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 300
INFO:>> Running issue grab for repo gwdetchar/gwdetchar, in page 4.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 400
INFO:>> Running issue grab for repo gwdetchar/gwdetchar, in page 5.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 492
INFO:492 issues returned from repo gwdetchar/gwdetchar at ../../data/all-issues_gwdetchar-gwdetchar_2025-11-13.json.
INFO:There are 492 issues for repo gwdetchar/gwdetchar.
INFO:Saved out issues data to ../../data/processed-issues_gwdetchar-gwdetchar_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 931 discussions for repo gwdetchar/gwdetchar.
INFO:There are 90 non-PR type issue ticket discussions for repo gwdetchar/gwdetchar.
INFO:There are 841 PR type issue ticket discussions for repo gwdetchar/gwdetchar.
INFO:Saved out ALL discussions data for repo gwdetchar/gwdetchar to ../../data/all-discussions_gwdetchar-gwdetchar_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo gwdetchar/gwdetchar to ../../data/non-PR-issue-discussions_gwdetchar-gwdetchar_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo gwdetchar/gwdetchar to ../../data/PR-issue-discussions_gwdetchar-gwdetchar_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 8 of 16
processing repo: qbic-pipelines/rnadeseq.
INFO:getting json via request url https://api.github.com/repositories/193906778/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/193906778/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/193906778/issues/comments?per_page=100&page=4.
INFO:There are 350 items across all pages.
INFO:Checking whether repo qbic-pipelines/rnadeseq has issues enabled.
Attempting to find issues content for repo: qbic-pipelines/rnadeseq
INFO:Running run_all_issues() to get all issues data for repo qbic-pipelines/rnadeseq.
INFO:Checking whether issue tickets data for repo qbic-pipelines/rnadeseq for today's date already exists at path ../../data/all-issues_qbic-pipelines-rnadeseq_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is qbic-pipelines/rnadeseq. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo qbic-pipelines/rnadeseq, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo qbic-pipelines/rnadeseq, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo qbic-pipelines/rnadeseq, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 284
INFO:284 issues returned from repo qbic-pipelines/rnadeseq at ../../data/all-issues_qbic-pipelines-rnadeseq_2025-11-13.json.
INFO:There are 284 issues for repo qbic-pipelines/rnadeseq.
INFO:Saved out issues data to ../../data/processed-issues_qbic-pipelines-rnadeseq_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 350 discussions for repo qbic-pipelines/rnadeseq.
INFO:There are 132 non-PR type issue ticket discussions for repo qbic-pipelines/rnadeseq.
INFO:There are 218 PR type issue ticket discussions for repo qbic-pipelines/rnadeseq.
INFO:Saved out ALL discussions data for repo qbic-pipelines/rnadeseq to ../../data/all-discussions_qbic-pipelines-rnadeseq_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo qbic-pipelines/rnadeseq to ../../data/non-PR-issue-discussions_qbic-pipelines-rnadeseq_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo qbic-pipelines/rnadeseq to ../../data/PR-issue-discussions_qbic-pipelines-rnadeseq_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 9 of 16
processing repo: ubermag/mag2exp.
INFO:There are 42 items across all pages.
INFO:Checking whether repo ubermag/mag2exp has issues enabled.
Attempting to find issues content for repo: ubermag/mag2exp
INFO:Running run_all_issues() to get all issues data for repo ubermag/mag2exp.
INFO:Checking whether issue tickets data for repo ubermag/mag2exp for today's date already exists at path ../../data/all-issues_ubermag-mag2exp_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is ubermag/mag2exp. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo ubermag/mag2exp, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 76
INFO:76 issues returned from repo ubermag/mag2exp at ../../data/all-issues_ubermag-mag2exp_2025-11-13.json.
INFO:There are 76 issues for repo ubermag/mag2exp.
INFO:Saved out issues data to ../../data/processed-issues_ubermag-mag2exp_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 42 discussions for repo ubermag/mag2exp.
INFO:There are 13 non-PR type issue ticket discussions for repo ubermag/mag2exp.
INFO:There are 29 PR type issue ticket discussions for repo ubermag/mag2exp.
INFO:Saved out ALL discussions data for repo ubermag/mag2exp to ../../data/all-discussions_ubermag-mag2exp_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo ubermag/mag2exp to ../../data/non-PR-issue-discussions_ubermag-mag2exp_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo ubermag/mag2exp to ../../data/PR-issue-discussions_ubermag-mag2exp_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 10 of 16
processing repo: ubermag/micromagneticmodel.
INFO:There are 82 items across all pages.
INFO:Checking whether repo ubermag/micromagneticmodel has issues enabled.
Attempting to find issues content for repo: ubermag/micromagneticmodel
INFO:Running run_all_issues() to get all issues data for repo ubermag/micromagneticmodel.
INFO:Checking whether issue tickets data for repo ubermag/micromagneticmodel for today's date already exists at path ../../data/all-issues_ubermag-micromagneticmodel_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is ubermag/micromagneticmodel. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo ubermag/micromagneticmodel, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 97
INFO:97 issues returned from repo ubermag/micromagneticmodel at ../../data/all-issues_ubermag-micromagneticmodel_2025-11-13.json.
INFO:There are 97 issues for repo ubermag/micromagneticmodel.
INFO:Saved out issues data to ../../data/processed-issues_ubermag-micromagneticmodel_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 82 discussions for repo ubermag/micromagneticmodel.
INFO:There are 22 non-PR type issue ticket discussions for repo ubermag/micromagneticmodel.
INFO:There are 60 PR type issue ticket discussions for repo ubermag/micromagneticmodel.
INFO:Saved out ALL discussions data for repo ubermag/micromagneticmodel to ../../data/all-discussions_ubermag-micromagneticmodel_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo ubermag/micromagneticmodel to ../../data/non-PR-issue-discussions_ubermag-micromagneticmodel_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo ubermag/micromagneticmodel to ../../data/PR-issue-discussions_ubermag-micromagneticmodel_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 11 of 16
processing repo: ubermag/ubermagtable.
INFO:There are 38 items across all pages.
INFO:Checking whether repo ubermag/ubermagtable has issues enabled.
Attempting to find issues content for repo: ubermag/ubermagtable
INFO:Running run_all_issues() to get all issues data for repo ubermag/ubermagtable.
INFO:Checking whether issue tickets data for repo ubermag/ubermagtable for today's date already exists at path ../../data/all-issues_ubermag-ubermagtable_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is ubermag/ubermagtable. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo ubermag/ubermagtable, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 65
INFO:65 issues returned from repo ubermag/ubermagtable at ../../data/all-issues_ubermag-ubermagtable_2025-11-13.json.
INFO:There are 65 issues for repo ubermag/ubermagtable.
INFO:Saved out issues data to ../../data/processed-issues_ubermag-ubermagtable_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 38 discussions for repo ubermag/ubermagtable.
INFO:There are 10 non-PR type issue ticket discussions for repo ubermag/ubermagtable.
INFO:There are 28 PR type issue ticket discussions for repo ubermag/ubermagtable.
INFO:Saved out ALL discussions data for repo ubermag/ubermagtable to ../../data/all-discussions_ubermag-ubermagtable_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo ubermag/ubermagtable to ../../data/non-PR-issue-discussions_ubermag-ubermagtable_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo ubermag/ubermagtable to ../../data/PR-issue-discussions_ubermag-ubermagtable_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 12 of 16
processing repo: FlicAnderson/thisrepodoesnotexist.
ERROR:Encountered repo-getting-workflow-borking error in repo FlicAnderson/thisrepodoesnotexist; Repo DOES NOT EXIST or is private: API response not OK for repo FlicAnderson/thisrepodoesnotexist; API response is: <Response [404]>; headers are: {'Date': 'Thu, 13 Nov 2025 14:00:30 GMT', 'Content-Type': 'application/json; charset=utf-8', 'github-authentication-token-expiration': '2026-01-20 14:48:08 +0000', 'X-GitHub-Media-Type': 'github.v3; format=json', 'x-accepted-github-permissions': 'issues=read; pull_requests=read', 'x-github-api-version-selected': '2022-11-28', 'X-RateLimit-Limit': '5000', 'X-RateLimit-Remaining': '4819', 'X-RateLimit-Reset': '1763045893', 'X-RateLimit-Used': '181', 'X-RateLimit-Resource': 'core', 'Access-Control-Expose-Headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset', 'Access-Control-Allow-Origin': '*', 'Strict-Transport-Security': 'max-age=31536000; includeSubdomains; preload', 'X-Frame-Options': 'deny', 'X-Content-Type-Options': 'nosniff', 'X-XSS-Protection': '0', 'Referrer-Policy': 'origin-when-cross-origin, strict-origin-when-cross-origin', 'Content-Security-Policy': "default-src 'none'", 'Vary': 'Accept-Encoding, Accept, X-Requested-With', 'Content-Encoding': 'gzip', 'Transfer-Encoding': 'chunked', 'Server': 'github.com', 'X-GitHub-Request-Id': 'C55B:126250:12081DC:166145A:6915E47E'}.
processing repo 13 of 16
processing repo: FlicAnderson/peramagroon.
INFO:There are 0 items across all pages.
INFO:Checking whether repo FlicAnderson/peramagroon has issues enabled.
Attempting to find issues content for repo: FlicAnderson/peramagroon
INFO:Running run_all_issues() to get all issues data for repo FlicAnderson/peramagroon.
INFO:Checking whether issue tickets data for repo FlicAnderson/peramagroon for today's date already exists at path ../../data/all-issues_FlicAnderson-peramagroon_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is FlicAnderson/peramagroon. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo FlicAnderson/peramagroon, in page 1.
INFO:API response is: <Response [200]>
ERROR:Result of API request is an empty json. Error - cannot currently handle this result nicely. Traceback: NoneType: None

INFO:all_issues length is now 0
INFO:0 issues returned from repo FlicAnderson/peramagroon at ../../data/all-issues_FlicAnderson-peramagroon_2025-11-13.json.
INFO:There are 0 issues for repo FlicAnderson/peramagroon.
ERROR:Repo FlicAnderson/peramagroon has no issues to query. Frame is None or pd.DataFrame is empty; perhaps no issues?
processing repo 14 of 16
processing repo: FlicAnderson/PR_test.
INFO:There are 5 items across all pages.
INFO:Checking whether repo FlicAnderson/PR_test has issues enabled.
Attempting to find issues content for repo: FlicAnderson/PR_test
INFO:Running run_all_issues() to get all issues data for repo FlicAnderson/PR_test.
INFO:Checking whether issue tickets data for repo FlicAnderson/PR_test for today's date already exists at path ../../data/all-issues_FlicAnderson-PR_test_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is FlicAnderson/PR_test. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo FlicAnderson/PR_test, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 4
INFO:4 issues returned from repo FlicAnderson/PR_test at ../../data/all-issues_FlicAnderson-PR_test_2025-11-13.json.
INFO:There are 4 issues for repo FlicAnderson/PR_test.
INFO:Saved out issues data to ../../data/processed-issues_FlicAnderson-PR_test_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 5 discussions for repo FlicAnderson/PR_test.
INFO:There are 1 non-PR type issue ticket discussions for repo FlicAnderson/PR_test.
INFO:There are 4 PR type issue ticket discussions for repo FlicAnderson/PR_test.
INFO:Saved out ALL discussions data for repo FlicAnderson/PR_test to ../../data/all-discussions_FlicAnderson-PR_test_2025-11-13.csv.
INFO:Saved out non-pull-request discussions data for repo FlicAnderson/PR_test to ../../data/non-PR-issue-discussions_FlicAnderson-PR_test_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo FlicAnderson/PR_test to ../../data/PR-issue-discussions_FlicAnderson-PR_test_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
processing repo 15 of 16
processing repo: riboviz/riboviz.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=2.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=3.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=4.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=5.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=6.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=7.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=8.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=9.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=10.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=11.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=12.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=13.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=14.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=15.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=16.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=17.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=18.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=19.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=20.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=21.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=22.
INFO:getting json via request url https://api.github.com/repositories/184749972/issues/comments?per_page=100&page=23.
INFO:There are 2243 items across all pages.
INFO:Checking whether repo riboviz/riboviz has issues enabled.
Attempting to find issues content for repo: riboviz/riboviz
INFO:Running run_all_issues() to get all issues data for repo riboviz/riboviz.
INFO:Checking whether issue tickets data for repo riboviz/riboviz for today's date already exists at path ../../data/all-issues_riboviz-riboviz_2025-11-13.json.
INFO:No existing issues file found; getting issues via GH API.
INFO:Repo name is riboviz/riboviz. Getting issues.
INFO:issue_links: multipage function used.
INFO:>> Running issue grab for repo riboviz/riboviz, in page 1.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 100
INFO:>> Running issue grab for repo riboviz/riboviz, in page 2.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 200
INFO:>> Running issue grab for repo riboviz/riboviz, in page 3.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 300
INFO:>> Running issue grab for repo riboviz/riboviz, in page 4.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 400
INFO:>> Running issue grab for repo riboviz/riboviz, in page 5.
INFO:API response is: <Response [200]>
INFO:all_issues length is now 483
INFO:483 issues returned from repo riboviz/riboviz at ../../data/all-issues_riboviz-riboviz_2025-11-13.json.
INFO:There are 483 issues for repo riboviz/riboviz.
INFO:Saved out issues data to ../../data/processed-issues_riboviz-riboviz_2025-11-13.csv.
INFO:Wrote out processed issues data to csv.
INFO:There are 2243 discussions for repo riboviz/riboviz.
INFO:There are 2064 non-PR type issue ticket discussions for repo riboviz/riboviz.
INFO:There are 179 PR type issue ticket discussions for repo riboviz/riboviz.
INFO:Saved out ALL discussions data for repo riboviz/riboviz to ../../data/all-discussions_riboviz-riboviz_2025-11-13.csv.
Index(['url', 'html_url', 'issue_url', 'id', 'node_id', 'user', 'created_at',
       'updated_at', 'body', 'author_association', 'reactions',
       'performed_via_github_app', 'issue_id_number',
       'discussion_author_gh_username'],
      dtype='object')
INFO:Saved out non-pull-request discussions data for repo riboviz/riboviz to ../../data/non-PR-issue-discussions_riboviz-riboviz_2025-11-13.csv.
INFO:Saved out pull-request discussions data for repo riboviz/riboviz to ../../data/PR-issue-discussions_riboviz-riboviz_2025-11-13.csv.

All discussions filesizes seem good for the 16 test repos (ie no file created for non-exist repo, no content for peramagroon repo which has no issue tickets, so files have size 2, rest look good).

Next try reading in and comparing to output messages.

[FlicAnderson]

Error on the run...

# bunch more output... 
# 
processing repo: SINTEF/dlite.
processing repo 697 of 1284
processing repo: CH-Earth/summa.
Traceback (most recent call last):
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/get_all_PR_code_reviews.py", line 361, in <module>
    get_code_reviews.loop_over_repos(repo_list=repo_list, get_type="discussions")
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/get_all_PR_code_reviews.py", line 270, in loop_over_repos
    discussions.get_all_discussions()
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/get_all_issue_ticket_discussions.py", line 244, in get_all_discussions
    PR_issues, non_PR_issues = self.split_issues_by_PR_status()
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/get_all_issue_ticket_discussions.py", line 170, in split_issues_by_PR_status
    processed_issues = self.get_issues_content()
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/get_all_issue_ticket_discussions.py", line 165, in get_issues_content
    return runissues.run_all_issues()
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/issues_workflow.py", line 219, in run_all_issues
    self.__save_formatted_issues(issues_df=processed_issues)
  File "/home/eidf103/eidf103/flic/clonezone/coding-smart/githubanalysis/processing/issues_workflow.py", line 179, in __save_formatted_issues
    issues_df.to_csv(path_or_buf=write_out, mode="w", index=True, header=True)
  File "/home/eidf103/eidf103/flic/.conda/envs/coding-smart-github/lib/python3.10/site-packages/pandas/core/generic.py", line 3902, in to_csv
    return DataFrameRenderer(formatter).to_csv(
  File "/home/eidf103/eidf103/flic/.conda/envs/coding-smart-github/lib/python3.10/site-packages/pandas/io/formats/format.py", line 1152, in to_csv
    csv_formatter.save()
  File "/home/eidf103/eidf103/flic/.conda/envs/coding-smart-github/lib/python3.10/site-packages/pandas/io/formats/csvs.py", line 266, in save
    self._save()
  File "/home/eidf103/eidf103/flic/.conda/envs/coding-smart-github/lib/python3.10/site-packages/pandas/io/formats/csvs.py", line 271, in _save
    self._save_body()
  File "/home/eidf103/eidf103/flic/.conda/envs/coding-smart-github/lib/python3.10/site-packages/pandas/io/formats/csvs.py", line 309, in _save_body
    self._save_chunk(start_i, end_i)
  File "/home/eidf103/eidf103/flic/.conda/envs/coding-smart-github/lib/python3.10/site-packages/pandas/io/formats/csvs.py", line 320, in _save_chunk
    libwriters.write_csv_rows(
  File "writers.pyx", line 55, in pandas._libs.writers.write_csv_rows
_csv.Error: need to escape, but no escapechar set

real    215m50.421s
user    9m16.402s
sys     0m24.166s

Same bug as a previous, so added the same fix (adding the escapechar to the .to_csv() call) and re-ran on a copy of the input repo names data file, but with everything up to the one before the failed repo removed, so it doesn't need to retry all those.