Fetch issue comments using GitHub Issue API for each GitHub Handle

[Rabia2219]

Overview

We need to use the GitHub Issue API to fetch issue comments for each GitHub handle so that we can use the data to generate skills learnt and resume-ready bullet points

Action Items

• Write GHA to Fetch All Issue Comments
  • Use GET /repos/{owner}/{repo}/issues/comments to fetch all issue comments for poc issues in the repo repo
  • Authenticate using a GitHub personal access token
  • Handle pagination to retrieve all comments
  • have it write it to the repo
• Bring results back to team meeting to discuss

Resources/Instructions

repo for issues: https://github.com/hackforla/website

GitHub handles for issues

• JackRichman
• JasonUranta
• mgodoy2023
• Zak234
• anonymousanemone

Config files for the script that chooses users etc (YAML)

• Config files

[ExperimentsInHonesty]

Read

• Create wiki to store information for reuse on this project #5 (comment)

[ExperimentsInHonesty]

@JasonUranta Please provide update

Instructions

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

You can use this template

1. Progress: 
2. Blockers: 
3. Availability:
4. ETA:
5. Pictures (if necessary): 

[JasonUranta]

1. Progress: Read through a significant amount of GitHub Docs and guides for how GHAs work and what roles they can fufill. including the resource links in Issue Create wiki to store information for reuse on this project #5 that Bonnie recommended
2. Blockers: While I understand the GHAs well in theory, I'm not sure what practical application and implementation look like so I'd like to delve deeper into working on using them. I'm also not 100% sure on how to tie them into the overall project my team is working on.
3. Availability: I'll have more time to work this week up until the weekend.
4. ETA: I should be able to make significant progress this coming week and have something concrete to present by next meeting.
5. Pictures (if necessary): N/A

[Rabia2219]

@JasonUranta Please provide update

Instructions

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

You can use this template

1. Progress: 
2. Blockers: 
3. Availability:
4. ETA:
5. Pictures (if necessary): 

[JasonUranta]

1. Progress: Worked on a py script and YAML file workflow to pull comments from needed users and repo. I ran the py file locally to make sure it works, but have yet to test the YAML file. Got more familar with how GHAs and API in the context of GHAs work with some trial and error.
2. Blockers: Currently trying to push my files into a branch i made on the repo but the terminal interface is telling me I don't have access to do so. Not sure if I have proper access to contribute to the project or if I should fork the repo and try to push it that way to make a PR.
3. Availability: I didn't have time to review Sandy's PR this weekend, but I can later today or tomorrow.
4. ETA: N/A
5. Pictures (if necessary): N/A

[JasonUranta]

Information on how to contribute is needed:

• When I tried to push the branch I made upstream to the repo, the CLI told me that I did not have the right access to do so.
• Is this an intentional security barrier? If so, how do I navigate it?
• Do I need better access permissions to contribute directly, or should I fork the repo first and push my work there so that I can later make a PR to contribute to the main repo?

[JasonUranta]

1. Progress: Submitted my PR for this issue and submitted my review comments on Sandy's PR. Added Andrew as a reviewer to that PR and messaged him on Slack.
2. Blockers: I think the next step for me is to wait on my PR to be reviewed and complete any revisions that may be needed.
3. Availability: Available now till August 7th but will be out of town from August 8th-15th, and uncertain if I will have my computer to do work. I will miss the meeting on August 11th.
4. ETA: N/A
5. Pictures (if necessary): N/A

[ExperimentsInHonesty]

Poc will be all the issues for a person on the website repo
repo:hackforla/website involves:JasonUranta
https://github.com/search?q=repo%3Ahackforla%2Fwebsite+involves%3AJasonUranta&type=issues
4 issues, 7 PRs

Pilot will be all the issues for a person across all HackforLA repos
org:hackforla involves:JasonUranta
https://github.com/search?q=org%3Ahackforla+involves%3AJasonUranta&type=issues
9 issues, 9 PRs