GitHub Actions: Automatically move a newly created issue into the Project Board

[macho-catt]

trafficstars

Overview

As a developer, we have to ensure that our kanban board is organized for all teams so that productivity is high. For this issue, we want newly created issues to automatically be placed in the Project Board.

Action Items

• [x] Review the notes below to understand the GitHub actions architecture we are currently moving towards
• [ ] This should be a new job under the "Issue Trigger" workflow
  • [ ] This job triggers on issue open
  • [ ] This job should have an if statement that triggers when the event name is "issues" and event action is "opened."
    • if: ${{ github.event_name == 'issues' && github.event.action == 'opened'}}
  • [ ] This job should run in parallel with the other action, "Add-Missing-Labels-To-Issues"

Pseudo-code

• [ ] When an issue is opened
  • [ ] Create a new project card in the Project Board "New Issue Approval" Column and assign this issue's ID in that card

Checks

• [ ] Test in your local environment that it works
• [ ] If a user creates an issue and does not add the issue to the Project Board, the GitHub action should automatically add the issue to the Project Board in the right column
• [ ] If a user creates an issue and adds it properly to the Project Board, the GitHub action should also add the issue to the correct column in the Project Board
• [ ] If the column the issue is going to has automation turned on, the GitHub action should still trigger and add the issue to the right column without causing any weird issues / side effects

Resources/Instructions

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[bot]]

Hi @macho-catt.

Good job adding the required labels to this issue.

Just a friendly reminder to also move the issue into the "New Issue Approval" column under the Project Board. For more info on that, check Github's documentation here. Thanks!

Additional Resources: Wiki: How to add status labels to issues (WIP. Link will be updated when the wiki is done) Wiki: How to create issues (WIP. Link will be updated when the wiki is done)

[github-actions[bot]]

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

[clayton1111]

Availability: all week ETA: 7/25

[ExperimentsInHonesty]

@clayton1111 given that the 29th is your last day, and you have not yet submitted a pr. Are you going to submit one or will you be annotating this issue. I am concerned if you submit a pr and then are not able to fix any changes anyone finds, that it will tie the whole thing up.

[clayton1111]

@ExperimentsInHonesty Figuring out how to test the GHA took a lot longer than I was expecting, so I have been working on creating a guide to explain how to to test GHA items. My plan is to annotate this issue since I won't have enough time to submit a PR and give reviewers enough time to fix everything!

[clayton1111]

Updates: Did not finish issue because I had difficulties figuring out how to test GHAs locally and my internship is ending. Changed focus to help create a guide explaining how to test GHAs. Link to act library that lets you test GHAs locally.

[github-actions[bot]]

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

[lilyarj]

Availability: 3hrs ETA: 9/20

[github-actions[bot]]

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

[KazushiR]

Availability: 6hrs ETA: 02/26/2023

[KazushiR]

1. Progress Looking into articles related to Github Actions
2. Blockers Figuring out how to use Github Actions
3. Availability Weekdays
4. ETA 03/06/2023

[KazushiR]

Progress Working on making a testing environment for my workflow Blockers Looking at the secrets page to link my workflow to the project pages. Availability Weekdays ETA N/A

[KazushiR]

unassigning myself from this issue due to the wording of the direction the nature of the problem.

[jdingeman]

Reworded to make it clearer. Adding it back to the prioritized backlog.

[github-actions[bot]]

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

[perlaroyerc]

Availability: 11-7 ET M-F ETA: April 3 2023

[perlaroyerc]

Progress: Learning how to create actions and run jobs in parallel. Blockers: No blockers, only tons of material to read. Availability: 11-7 ET M-F ETA: 4/7/23

[perlaroyerc]

Progress: Created a job that triggers when an issue is opened. Blockers: Learning how to test this action locally. Availability: 11-7 ET M-F ETA: 4/21/23

[github-actions[bot]]

@perlaroyerc

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 developer meeting discussion column 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, May 9, 2023 at 12:15 AM PST.}

[ExperimentsInHonesty]

@perlaroyerc Please either provide an update or unassign yourself from the issue and put it in the questions and review column with a comment.

[github-actions[bot]]

@perlaroyerc

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 developer meeting discussion column 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, May 16, 2023 at 12:16 AM PST.}

[github-actions[bot]]

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

[adrianang]

• Availability: MTWThSu, 6 PM - 10 PM (PST) (Weeks of 7/17, 7/24)
• ETA: I plan on finishing this issue by Monday, 7/24 at 10 PM.

[github-actions[bot]]

@adrianang

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' 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, July 25, 2023 at 12:15 AM PST.}

[adrianang]

Progress: Still working on the issue; have mostly been reading through the resources on GHA and looking at PRs related to GHA/automation. Blockers: No current blockers. Availability:

• Saturdays/Sundays: Generally from 2 PM - 8 PM PST
• Weekdays, excluding Wednesdays: Generally from 6 PM - 10 PM PST

ETA: Tuesday, 8/1 by 10 PM

[github-actions[bot]]

@adrianang

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' 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, August 8, 2023 at 12:06 AM PST.}

[github-actions[bot]]

@adrianang

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, August 15, 2023 at 12:05 AM PST.}

[github-actions[bot]]

@adrianang

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, August 22, 2023 at 12:06 AM PST.}

[adrianang]

Progress: Continuing/coming back to work on this issue; my first attempt wasn't too fruitful and I confused myself a bit, but I think I have a better idea on approaching this issue after looking at some of the other scripts and GHA issues. Availability: Saturdays/Sundays: Generally from 2 PM - 8 PM PST Weekdays, excluding Wednesdays: Generally from 6 PM - 10 PM PST ETA: Friday, 9/1 by 10 PM

[github-actions[bot]]

@adrianang

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' 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 5, 2023 at 12:05 AM PST.}