CivicTechJobs icon indicating copy to clipboard operation
CivicTechJobs copied to clipboard

Fix GitHub Action Issue Trigger

Open kcoronel opened this issue 1 year ago • 2 comments

Overview

When creating a new issue team members are getting a notification of an issue trigger. Relevant links are listed under Resources. Who ever takes on this issue should write out the Action Items needed to solve the issue.

Action Items

Resources/Instructions

  • https://github.com/orgs/hackforla/projects/37?pane=issue&itemId=67501179
  • https://github.com/hackforla/CivicTechJobs/actions/runs/11020112231

kcoronel avatar Sep 25 '24 08:09 kcoronel

I believe what's supposed to happen is that when a new issue in this repo is created, it should automatically be added to the project board New Issue Approval column. But I need someone to verify.

Steps to reproduce:

  1. Create a new issue in the repo (https://github.com/hackforla/CivicTechJobs )
  2. Check your email for a github workflow failed alert titled "Run failed: Issue Trigger - main"

Action Items

  • [x] Need someone to investigate what is happening here, what is this action doing, what is it supposed to do, why is it bugging out now.

Once we know what its supposed to do, we can decide if we want to:

  • [ ] (A) keep and fix it, or
  • [x] (B) just remove it and turn it off altogether

LoTerence avatar Sep 26 '24 21:09 LoTerence

screenshot: image

LoTerence avatar Sep 26 '24 23:09 LoTerence

I examined the GitHub action error and YAML file and now understand that:

  • The action was supposed to put newly opened issues in the "new issue approval" column on the project board.

  • The reason it hasn't been working is because we have a new project board, so either the token or the IDs used in the code (or both) are obsolete and GitHub couldn't find the project board.

  • The new project board has some handy settings for workflow controls now, so I played around with it and set up a workflow that does exactly what the action was trying to do.

  • I tested the workflow by opening new issues, and it indeed worked, so I think we can delete this GitHub action.

@LoTerence if this sounds good to you, I can submit a pull request to the develop branch. However, to actually stop this GitHub action (and its error), the change will need to be merged into the main branch eventually, correct?

bzzz-coding avatar Oct 24 '24 18:10 bzzz-coding

Yeah solution sounds good! For this one, go ahead and make a pull request into the main branch if you can

I will make sure its removed from develop once I get around to merging develop back into main

LoTerence avatar Oct 24 '24 22:10 LoTerence