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.

Sign up for GitHub

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

Jump to bottom

Create GHA to add comments to prework issues documenting issues events #4820

Open
20 tasks done
roslynwythe opened this issue Jun 12, 2023 · 6 comments · May be fixed by #6873
Open
20 tasks done

Create GHA to add comments to prework issues documenting issues events #4820

roslynwythe opened this issue Jun 12, 2023 · 6 comments · May be fixed by #6873
Assignees
@partapparam
Labels
Complexity: Extra Large Feature: Onboarding/Contributing.md Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 5pt Can be done in 19-30 hours
Projects
Project Board
Milestone
08. Team workflow

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Jun 12, 2023 •
edited by partapparam
Loading

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

  • Become familiar with HfLA's GitHub Actions and HfLA's GitHub Actions wiki page
  • The following event/activity types should trigger workflows/actions:
    • issues: opened, assigned, unassigned, closed as completed, or closed as not planned
    • issue_comment: created
    • pull_request: opened, closed
    • pull_request_review: submitted
    • pull_request_review_comment: created
  • Create one or more new jobs and/or actions to:
    • Determine the contributor generating the event/activity:
      • for opened issue events - the issue author
      • for assigned, unassigned, and closed issue events- the issue assignee
      • for issue_comment 'created` events - the comment author
      • for pull_request - the PR author
      • for pull_request_review and pull_request_review_comment - the reviewer or comment author
    • Search for an issue with a "prework" label that is assigned to the contributor
    • If the prework issue is closed, reopen it and put it in the "In Progress" column
    • 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

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

Resources/Instructions
@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing Draft Issue is still in the process of being created labels Jun 12, 2023
@roslynwythe roslynwythe changed the title create GHA to append comments to pre-work issues documenting dev activity Create GHA to append comments to pre-work issues documenting dev activity Jun 13, 2023
@roslynwythe roslynwythe changed the title Create GHA to append comments to pre-work issues documenting dev activity Create GHA to add comments to pre-work issues documenting dev activity Jun 13, 2023
@roslynwythe roslynwythe added Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers and removed role missing Feature Missing This label means that the issue needs to be linked to a precise feature label. labels Jun 14, 2023
@roslynwythe roslynwythe added this to New Issue Approval in Project Board via automation Jun 14, 2023
@roslynwythe roslynwythe mentioned this issue Jun 23, 2023
Open
2 tasks
@roslynwythe roslynwythe added ready for product size: 5pt Can be done in 19-30 hours and removed Draft Issue is still in the process of being created size: 3pt Can be done in 13-18 hours labels Jun 26, 2023
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Jun 27, 2023
@roslynwythe roslynwythe added the Draft Issue is still in the process of being created label Jul 26, 2023
@roslynwythe roslynwythe changed the title Create GHA to add comments to pre-work issues documenting dev activity Create GHA to add comments to prework issues documenting issues events Sep 29, 2023
@roslynwythe

This comment was marked as resolved.

Sign in to view
@roslynwythe roslynwythe added ready for product and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Sep 29, 2023
@ExperimentsInHonesty

This comment was marked as resolved.

Sign in to view
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Nov 6, 2023
@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created ready for dev lead Issues that tech leads or merge team members need to follow up on labels Nov 13, 2023
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Prioritized backlog in Project Board Nov 14, 2023
Closed
34 tasks
@partapparam partapparam self-assigned this May 8, 2024
@partapparam partapparam moved this from Prioritized backlog to In progress (actively working) in Project Board May 8, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented May 8, 2024

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 :)

@partapparam
Copy link
Member

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

@github-actions github-actions bot added the To Update ! No update has been provided label May 17, 2024
@github-actions GitHub Actions
Copy link

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

@partapparam partapparam added Status: Updated No blockers and update is ready for review and removed To Update ! No update has been provided labels May 17, 2024
@partapparam
Copy link
Member

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 partapparam linked a pull request May 21, 2024 that will close this issue
Open
@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label May 24, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the GHA New Project Board compatible This GitHub Action issue does not reference columns and will work with the new board label Jun 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms and removed GHA New Project Board compatible This GitHub Action issue does not reference columns and will work with the new board labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@partapparam partapparam

Labels
Complexity: Extra Large Feature: Onboarding/Contributing.md Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 5pt Can be done in 19-30 hours
Projects
HfLA Website: Project Board
Status: In progress (actively working)
Project Board
  
In progress (actively working)
Milestone
08. Team workflow
Development

Successfully merging a pull request may close this issue.

GHA add comments to prework issue 4820 partapparam/website
3 participants
@roslynwythe @partapparam @ExperimentsInHonesty