Prep for Project Board Migration: GitHub Actions / Workflows Part 1 of 2

[t-will-gillis]

Overview

In preparation for the migration to the Project Board Beta (PBB), we need to determine whether our existing GitHub Actions workflows will continue performing as we expect, or whether minor edits or major refactoring will be required.

Details

After some initial testing, it appears that many or most of our automations will continue working as expected. The major exceptions are workflows that reference a 'column' since this terminology is no longer used on the new board (the PBB refers to 'status' instead.) Following is a preliminary list of affected workflows and issues that will need to be made.

Action Items

Pre Migration

Following is a preliminary list of issues that will need to be made and completed

• Prep for Project Board Migration: Configure "Automatic workflows" #6995
• Project Board Migration: refactoring of "Issue Trigger" workflow #6996
• Project Board Migration: refactoring of "Pull Request Trigger" workflow #6997
• Project Board Migration: refactoring of "Schedule Friday 0700" workflow  #6998
• Project Board Migration: refactoring of "Move Closed Issues" workflow #7039

Post Migration

• Post migration issues needed after above issues are closed:
  • Post PBB migration: Refactor "Issue Trigger"  #7075 for issues with title "Hack for LA website bot..." from "inactive members", new issue previously was shuffled to "Questions / In Review" column >
  • Post PBB migration: Refactor "Pull Request Trigger" workflow #7076
  • Post PBB migration: Refactor "Schedule Friday" workflow #7078
  • Post PBB migration: Refactor "Move Closed Issues" workflow #7079

Once Above Issues Are Completed

• Close this issue

Resources/Instructions

• Sunset notice- Projects (classic)

[t-will-gillis]

All remaining issues written and ready to be worked on (after dependencies)

[t-will-gillis]

awaiting final issue #7079

[HackforLABot]

@t-will-gillis

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.

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, September 10, 2024 at 12:04 AM PST.}

[t-will-gillis]

still awaiting final issue #7079

[t-will-gillis]

Closing as completed