Move old, closed issues off the Project Board

[SAUMILDHANKAR]

Overview

As a developer, I want to move old, closed issues (that are in the Done column) from the "Project Board" to the "Issues Closed 13 months or more" project so that the Project Board becomes easier to manage and faster to respond.

Action Items

• Please go through the wiki article on Hack for LA's GitHub Actions
• Review the files in the following directories: website/.github and website/github-actions
• Note: Issues that are closed and have been in the done column for more than 30 days should be moved from the "Project Board" to the "Issues Closed 13 months or more" project
• This automation should run weekly.
• Analyze if a new GitHub action should be created or any of the existing actions can be modified.
• Add the code logic to implement this functionality in your own repo first.
• Make sure existing functionalities are not impacted and finally create a pull request.

Checks

• Test in your local environment that it works
• Issues that are closed and have been in the done column for 30 days should automatically be moved to a new project board
• Issues that are open and in the done column shouldn't be moved to the new project board.

Resources/Instructions

Project Board
Issues Closed 13 months or more project
Never done GitHub actions? Start here!
GitHub Complex Workflows doc
GitHub Actions Workflow Directory
Events that trigger workflows
Workflow syntax for GitHub Actions
actions/github-script
GitHub RESTAPI

Architecture Notes

The idea behind the refactor is to organize our GitHub Actions so that developers can easily maintain and understand them. Currently, we want our GitHub Actions to be structured like so based on this proposal:

• Schedules (military time)
  - Schedule Friday 0700
  - Schedule Thursday 1100
  - Schedule Daily 1100
• Linters
  - Lint SCSS
• PR Trigger
  - Add Linked Issue Labels to Pull Request
  - Add Pull Request Instructions
• Issue Trigger
  - Add Missing Labels To Issues
• WR - PR Trigger
  - WR Add Linked Issue Labels to Pull Request
  - WR Add Pull Request Instructions
• WR - Issue Trigger

Actions with the same triggers (excluding linters, which will be their own category) will live in the same github action file. Scheduled actions will live in the same file if they trigger on the same schedule (i.e. all files that trigger everyday at 11am will live in one file, while files that trigger on Friday at 7am will be on a separate file).

That said, this structure is not set in stone. If any part of it feels strange, or you have questions, feel free to bring it up with the team so we can evolve this format!

[github-actions]

Hi @SAUMILDHANKAR.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[Carlos-A-P]

Availability: 2 week
ETA: 6/01/2022

[kathrynsilvaconway]

Hi Carlos, I am moving this over to the 'in progress' column for you.

[Carlos-A-P]

1. Progress - Currently still learning how to approach this issue while I'm learning more about GitHub actions
2. Blockers - no blockers at the moment
3. Availability - 1 week
4. ETA - 6/8/2022

[ExperimentsInHonesty]

We will not be doing this automation. We have decided instead to use the archive feature.

[ExperimentsInHonesty]

I don't think there is a decision record for this. I am adding a ready for product label on it and sticking it in the new issue approval column so that we can write something up about the process.

[ExperimentsInHonesty]

We have resolved this by archiving the done column periodically.