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.

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

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

Open
20 tasks
roslynwythe opened this issue Jun 12, 2023 · 10 comments
Open
20 tasks
Assignees
Labels
Added to dev/pm agenda Complexity: Extra Large Draft Issue is still in the process of being created Feature: Onboarding/Contributing.md Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 5pt Can be done in 19-30 hours

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Jun 12, 2023

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 Complexity: Large size: 3pt Can be done in 13-18 hours and removed role missing Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing labels Jun 14, 2023
@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.

@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

This comment was marked as outdated.

@partapparam

This comment was marked as outdated.

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

This comment was marked as outdated.

@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

This comment was marked as outdated.

@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 moved this to In progress (actively working) in P: HfLA Website: Project Board Jun 23, 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
@partapparam

This comment was marked as outdated.

@partapparam partapparam removed their assignment Sep 30, 2024
@JessicaLucindaCheng JessicaLucindaCheng moved this from In progress (actively working) to New Issue Approval in P: HfLA Website: Project Board Oct 7, 2024
@JessicaLucindaCheng JessicaLucindaCheng added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Oct 7, 2024
@JessicaLucindaCheng
Copy link
Member

@t-will-gillis t-will-gillis self-assigned this Oct 8, 2024
@t-will-gillis t-will-gillis added the Draft Issue is still in the process of being created label Oct 8, 2024
@HackforLABot

This comment was marked as outdated.

@HackforLABot

This comment was marked as outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Added to dev/pm agenda Complexity: Extra Large Draft Issue is still in the process of being created Feature: Onboarding/Contributing.md Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 5pt Can be done in 19-30 hours
Projects
Status: New Issue Approval
Development

Successfully merging a pull request may close this issue.

6 participants