Bug: HackforLABot moving issues to wrong columns

[SAUMILDHANKAR]

Overview

As a developer, I want to fix the bug where the HackforLA bot is moving the issues to wrong columns so as to ensure that the bot actions are error free and helpful.

Action Items

• Review how and when HackforLA bot moves issues between different columns
• Analyze why the issue was moved from Done to QA in Pre-work Checklist: Developer: Shantanu Shende #2560 and DRAFT: Move the "...see more" to the bottom right of the card for each card on the Wins page #2707 and why the issue was moved from New Issue Approval to Done in GitHub Actions: Implement CodeQL #2400
• Review if changes to the following files might help in fixing the bug: Move closed issues yaml file,
  Sost closed issues js file
• Analyze if the project board automations might interfere with GitHub actions
• Check if there are any other scenarios where the issue might be moved unexpectedly
• Test the changes in your own repo and ensure existing functionalities are not impacted
• Make your recommendations or proposed solutions to tech leads or in a team meeting
• Create a PR that fixes this bug

Resources/Instructions

Issues where bug was encountered:
- Issues were moved from Done to QA: Case 1, Case 2
- Issue was moved from New Issue Approval to Done]
Helpful issue for review
Move closed issues yaml file
Sost closed issues js file

[github-actions]

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

[Zak234]

Availability: All day
ETA: 2-3 days

[Zak234]

I looked at the issues and it seems like the reason issues #2560 and #2707 were moved was due to poor labelling on the issues. For #2400, it looks like it was just an issue with the person accidentally closing and reopening their issue which caused the action to run. I discussed with the tech leads and Bonnie about whether we should change which labels send and prevent issues from going to the QA column and it was decided that the current code suits our needs.