GitHub Actions: 2 weeks inactive label bug

[SAUMILDHANKAR]

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 the 2 weeks inactive label should be posted only after 14 days of inactivity from the time the issue is assigned.

Action Items

• Review add-label.js file located at (https://github.com/hackforla/website/tree/gh-pages/github-actions/add-update-label-weekly)
• Add a condition which checks for the amount of time since issue was assigned, and adds a 2 weeks inactive label only if no comment or PR from the assignee.
• Release dependency on Refactoring: Multiple if else statements in add-label.js to be combined into functions #2652 and GitHub Actions: Improvements to 'Automate In Progress Issue Updates: Add Update Label' #2032
  • Update action items in the dependency issues if needed

Pseudo-code

• When 14 days have elapsed from the time of issue being assigned
  • Add 2 weeks inactive label if there is no comment or PR by assignee.

Checks

• Test in your local environment that it works
• If less than 14 days passed since issue was assigned, don't add 2 weeks inactive label.
• If less than 14 days passed since last comment by assignee, don't add 2 weeks inactive label.

Resources/Instructions

• General info about GHAs at hack for LA website: https://github.com/hackforla/website/wiki/Hack-for-LA's-GitHub-Actions
• Specific wiki page for this GHA: https://github.com/hackforla/website/wiki/GHA:-add-update-label-weekly

[github-actions]

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: 5hrs
ETA: 7/8

[ExperimentsInHonesty]

This issue shows that summer did an update but the issue #2763 still has the 2 week inactive label. What is supposed to happen

On this issue it shows it might be adding it to soon #2309

[ExperimentsInHonesty]

see this page https://github.com/hackforla/website/wiki/GHA:-add-update-label-weekly
https://github.com/hackforla/website/wiki/HfLA-GitHub-Actions

[github-actions]

@tunglinn

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 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.

_{You are receiving this comment because your last comment was before Monday, January 2, 2023 at 11:15 PM PST.}

[tunglinn]

1. Need to figure out what examples to give PR reviewers to test the code.
2. No blockers
3. 10-11 am on weekdays.
4. Friday

[tunglinn]

1. One thing I noticed about using the classic vs fine-grain token is that when I use fine-grain, events that should be labeled as "cross-referenced" are retrieved as "mentioned".

Therefore, if testing this issue, make sure to be using a classic token.

2. There are several method to solve this bug. All of them require some sort of refactoring. I'll be attending office hours this week to ask if this is allowed.

[github-actions]

@tunglinn

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 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.

_{You are receiving this comment because your last comment was before Monday, January 23, 2023 at 11:16 PM PST.}

[ExperimentsInHonesty]

@tunglinn Hope you are doing well. Can you provide an update on this issue, or move it back to the prioritized backlog if you are unable to continue.

[github-actions]

@tunglinn

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 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.

_{You are receiving this comment because your last comment was before Monday, February 6, 2023 at 11:17 PM PST.}

[tunglinn]

Having trouble finding time to work on this. I wouldn't mind sending it back to prioritized backlog, but I would prefer if I handed this off to someone else who can finish it ASAP, in which I could explain how to fix this issue.

[jdingeman]

Hi @tunglinn, just sent you a message via Slack. Putting this here as well.

Please provide us with a write up or a video recording of your attempts at resolving this issue, and what approaches you found that worked/didn't work and what the next dev working on this issue will need to look out for.

Thanks!