Create a Github Action to verify Pull Requests are created by website team members

MattPereira commented 1 year ago

Overview

As developers, we need to ensure that only members of our organization create pull requests to the hackforla / website repository. For this issue, we will add a github action that checks if the pull request creator is a member of the website team.

Action Items

[x] Learn how github actions work

[ ] Add a github action that checks if the creator of a pull request is a member of the website-write team

[ ] If the author is not a member of the website-write team, close the pull request with this comment:

You must be a member of the HFLA  website team in order to create pull requests. Please see our page on how to join us as a member at HFLA: https://www.hackforla.org/getting-started.  If you have been though onboarding, and feel this message in error, please message us in the #hfla-site team slack channel with the link to this PR.

Resources/Instructions

Wiki for writing new GHAs at HFLA: https://github.com/hackforla/website/wiki/HfLA-GitHub-Actions
Wiki for explaining HFLA GHA architecture: https://github.com/hackforla/website/wiki/Hack-for-LA's-GitHub-Actions

github-actions[bot] commented 1 year ago

Hi @KazushiR, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

KazushiR commented 1 year ago

i. Availability: Weekdays ii. ETA: N/A. I am trying to figure out how Github Actions work. Will give weekly updates on my progress.

KazushiR commented 1 year ago

Didn't realize this was in a draft file. Will be unassigning myself and moving this back new issue-approval

roslynwythe commented 8 months ago

@ExperimentsInHonesty If the GHA finds that a non-member has created a PR, perhaps the GHA should close the PR. Should I add that action to this issue?

ExperimentsInHonesty commented 6 months ago

@roslynwythe how often does it happen? If its only occasionally, then we should double check them.

roslynwythe commented 6 months ago

@roslynwythe how often does it happen? If its only occasionally, then we should double check them.

You mean double-check in case the GHA action was incorrect and the contributor is in fact a member of Hack for LA? My main concern is that a bot comment in a PR is not all that visible and it may not come to the attention of the contributor or the merge team, unless we can do something to increase visibility, like make it appear in red or somehow give it an appearance similar to a failed GitHub check or a request for change.

ExperimentsInHonesty commented 6 months ago

Agreed. Let's have it auto close the prs. Also lets add the same text in the close message on the pr template itself.

https://github.com/hackforla/website/blob/gh-pages/.github/pull_request_template.md

roslynwythe commented 5 months ago

Agreed. Let's have it auto close the prs. Also lets add the same text in the close message on the pr template itself.

https://github.com/hackforla/website/blob/gh-pages/.github/pull_request_template.md

@ExperimentsInHonesty I updated the issue so that if a pull request is created by a non-member, the PR is closed with a comment. I'm not sure I understand "Also lets add the same text in the close message on the pr template itself"

ExperimentsInHonesty commented 5 months ago

@roslynwythe I have created an ER to address the remaining items on this issue (adding it to the pr template)

github-actions[bot] commented 4 months ago

Hi @roychan1, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

roychan1 commented 4 months ago

i. Availability: 8am-5pm ii. ETA: I am hoping to complete the ticket or at least make significant progress by 1/17 Wednesday.

github-actions[bot] commented 4 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 22, 2024 at 11:05 PM PST.}

github-actions[bot] commented 4 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 PM PST.}

roychan1 commented 3 months ago

Progress: performing research on GitHub Actions
Blockers: I have been preoccupied with other responsibilities
Availability: this week
ETA: 2 weeks

github-actions[bot] commented 3 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 PM PST.}

github-actions[bot] commented 3 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 19, 2024 at 11:06 PM PST.}

ExperimentsInHonesty commented 3 months ago

@roychan1 You need to give updates every week, or we unassign you from the issue.

roychan1 commented 3 months ago

@roychan1 You need to give updates every week, or we unassign you from the issue.

I had been occupied and forgotten to provide updates or reassign the ticket, I apologize about that! I will be resuming my work on this issue and provide updates from now!

roychan1 commented 3 months ago

Progress: continue performing research on GitHub Actions and begin implementing
Blockers: I have been occupied with personal matters
Availability: 9am-5pm
ETA: 1 week

github-actions[bot] commented 2 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, March 4, 2024 at 11:06 PM PST.}

roychan1 commented 2 months ago

Progress: continue performing research on GitHub Actions and begin implementing
Blockers: busy schedule
Availability: 8am-5pm
ETA: 1 week

github-actions[bot] commented 2 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, March 19, 2024 at 12:06 AM PST.}

github-actions[bot] commented 2 months ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, March 26, 2024 at 12:06 AM PST.}

roychan1 commented 1 month ago

Progress: continue performing research on GitHub Actions and begin implementing
Blockers: I have been occupied with work
Availability: 9am-5pm
ETA: 1 week

github-actions[bot] commented 1 month ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, April 9, 2024 at 12:06 AM PST.}

github-actions[bot] commented 1 month ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, April 16, 2024 at 12:06 AM PST.}

github-actions[bot] commented 1 month ago

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, April 23, 2024 at 12:06 AM PST.}

LRenDO commented 1 month ago

Hi @roychan1! It seems like you've got a lot going on right now which is totally okay. I am going to remove you from this issue for now. If you feel you can complete in the next two weeks feel free to add yourself back. Otherwise, feel free to take on another issue when your availability opens up. Thanks!

github-actions[bot] commented 4 weeks ago

Hi @ajb176, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

ajb176 commented 4 weeks ago

ETA: 3 weeks Availability: Evenings

github-actions[bot] commented 2 weeks ago

@ajb176

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 14, 2024 at 12:06 AM PST.}

ajb176 commented 2 weeks ago

Have a rough idea of what the implementation needs to look like, still need to set up the testing environment and take a few hours to go through the Github API docs.
Nothing yet, will update this if necessary over the next two days
Will have a lot of time this weekend
Hope to finish by the end of this weekend if there are no blockers, latest by next weekend.

ajb176 commented 5 days ago

Progress: The control flow for verifying team membership seems like it's working properly, still need to test the API call that closes the PR. Blockers: None, but testing is time consuming Availability: Tuesday evening ETA: Sunday, if not done by Wednesday

hackforla / website