website icon indicating copy to clipboard operation
website copied to clipboard

Published 20 hours ago • verified publisher icon hackforla

Create GHA to add comments to prework issues documenting `issues` events

Open roslynwythe opened this issue 1 year ago • 6 comments

Overview

We need to create a GitHub Action that will be triggered by GitHub issue, issue_comment, pull_request, pull_request_review and pull_request_review_comment events and will post comments to the developer's pre-work issue describing the developer's activities.

Action Items

  • [x] Become familiar with HfLA's GitHub Actions and HfLA's GitHub Actions wiki page
  • [x] The following event/activity types should trigger workflows/actions:
    • [x] issues: opened, assigned, unassigned, closed as completed, or closed as not planned
    • [x] issue_comment: created
    • [x] pull_request: opened, closed
    • [x] pull_request_review: submitted
    • [x] pull_request_review_comment: created
  • [x] Create one or more new jobs and/or actions to:
    • [x] Determine the contributor generating the event/activity:
      • [x] for opened issue events - the issue author
      • [x] for assigned, unassigned, and closed issue events- the issue assignee
      • [x] for issue_comment 'created` events - the comment author
      • [x] for pull_request - the PR author
      • [x] for pull_request_review and pull_request_review_comment - the reviewer or comment author
    • [x] Search for an issue with a "prework" label that is assigned to the contributor
    • [x] If the prework issue is closed, reopen it and put it in the "In Progress" column
    • [x] Add a comment to the prework issue describing the event/activity
- #[ISSUE # or PR# or link to comment ] has been [ACTIVITY DESCRIPTION] by [REPLACE WITH CONTRIBUTOR GITHUB HANDLE]

where ACTIVITY DESCRIPTION is one of the activity types listed above

  • [x] Integrate the job into existing or new workflows with the appropriate triggers
  • [x] Test the new GHA using your copy of the Project Board

Resources/Instructions

roslynwythe avatar Jun 12 '23 23:06 roslynwythe

@ExperimentsInHonesty Please advise, if there is activity associated with a contributor but their prework issue is closed, should the prework issue be reopened?

roslynwythe avatar Sep 29 '23 09:09 roslynwythe

@roslynwythe

@ExperimentsInHonesty Please advise, if there is activity associated with a contributor but their prework issue is closed, should the prework issue be reopened?

Yes!

Newly reopened issues should be placed in the In Progress column

RW: Done!

ExperimentsInHonesty avatar Nov 06 '23 21:11 ExperimentsInHonesty

Hi @partapparam, 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 :)

github-actions[bot] avatar May 08 '24 19:05 github-actions[bot]

i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) 3pm - 6pm Thursday and Friday, 9am - 1pm Sunday, will update additional availability after Sunday ii. ETA: (When do you expect this issue to be completed?) - 5/17

partapparam avatar May 08 '24 19:05 partapparam

@partapparam

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.

  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 (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.

github-actions[bot] avatar May 17 '24 07:05 github-actions[bot]

Progress: "What is the current status of your project? What have you completed and what is left to do?"

  • I'm finishing up, currently working to reopen the issue and update the project board. Blockers: "Difficulties or errors encountered."
  • Not currently Availability: "How much time will you have this week to work on this issue?"
  • Today, 10-12pm, Sunday, 6-9 pm ETA: "When do you expect this issue to be completed?" 5/19

partapparam avatar May 17 '24 17:05 partapparam

Hi Team, I need to drop this issue. I'm unable to dedicate time to complete it due to some other commitments.

partapparam avatar Sep 30 '24 02:09 partapparam

  • I saw this issue as unassigned in the In Progress column and have moved it to the New Issue Approval column. It has an open PR https://github.com/hackforla/website/pull/6873 that Will was discussing with Param.

JessicaLucindaCheng avatar Oct 07 '24 22:10 JessicaLucindaCheng

Hi @t-will-gillis, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).

HackforLABot avatar Oct 08 '24 00:10 HackforLABot

Hi @t-will-gillis, 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 :)

HackforLABot avatar Oct 08 '24 01:10 HackforLABot