GitHub Actions: Improvements to 'Automate In Progress Issue Updates: Add Update Label'

[Aveline-art]

Dependency

• GitHub Actions: Automate In Progress Issue Updates: Flags Inactive #1977
• GitHub Actions: 2 weeks inactive label bug #2634

Overview

As a developer, we need to ensure that the GHA involving the 'To Update !' label creates clear comments and directions for the team to follow.

Action Items

• Understand the code from the below directories.
• JS Edits
  • Add a new filter in the isTimelineOutdated function to see when an issue is assigned. If an issue is assigned more than 3 days ago, the issue is considered outdated, and the label is added. This may not be required once GitHub Actions: 2 weeks inactive label bug #2634 is merged.
  • The timeline should indicate the timezone (which is set to PST). If possible, fix it in the formatComment function's options variable in the js file, rather than on the md file.
• MD edits
  • In the md file, add instructions to put questions in the issue if help is needed with pictures if needed, and that these are examples of well-formed questions: Develop Updated Getting Started page #1619 (comment) or Remove additional space from wins-card-mobile.svg within WIns About page (mobile only) #1908 (comment)
• Release dependency on GitHub Actions: Automate In Progress Issue Updates: Hide Old Comments #1976

Resources/Instructions

add-update-label-weekly
add-update-label-weekly.yml

Related Pages

#1956
#2006

Never done GitHub actions? Start here!

Note that you might want to do something outside the scope of the above psudo-code. If so, be sure to leave comments in your PR or this issue that justifies your reasoning. If you feel you need guidance, be sure to reach out! We cannot foresee whether this issue is solvable, or what hard decisions have to be made, but we would love to hear and help you!

Additional resources:

Events that trigger workflows
Workflow syntax for GitHub Actions
GitHub GraphQL

[macho-catt]

Putting this as a dependency because we found an interesting issue for #1977 that may be related to this. Basically, if an issue was recently assigned but it falls under the timing window for asking to update an issue, it asks for an update even though it was recently picked up.

@SAUMILDHANKAR tagging you for your info

[ExperimentsInHonesty]

I moved this out of the icebox and added the ready for dev lead labels because the dependencies are satisfied.

[github-actions]

Hi @t-will-gillis, 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 :)

[ExperimentsInHonesty]

@t-will-gillis are you working on the issue or drafting it?

• If you are drafting it, you can add a draft label and leave it in this column (new issue approval) while you complete the draft.
• If you are working on it. Then move it to in progress column

[github-actions]

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

[angieyan]

Availability: Mon - Wed 9am - 11am
ETA: May 4, 23 EOD

[t-will-gillis]

Hi @angieyan - thanks for your interest in this issue. Please note that the only issues in the Prioritized Backlog column are eligible to be worked on. This issue was in the New Issue Approval column and is not available for you to work on.

I will take care of us-assigning you from this issue and moving it back to the correct column. Please check out the CONTRIBUTING.md documents and available issues in the Prioritized Backlog column.

[github-actions]

Hi @t-will-gillis, 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 :)

[t-will-gillis]

Note: This issue is being rewritten for these reasons:

• Since it is an older issue, some of the steps listed in the 'JS Edits' have already been addressed by other issues, e.g. GitHub Actions: 2 weeks inactive label bug #2634 and GitHub Actions: Bot adding and removing "Status: Updated" and "To Update!" label #3341 and the comments already display the time in PST.
• The links to 'MD edits' and in 'Resources/ Instructions' are expired/ point to a 404 page.

Since deleting and/or striking the expired instructions will make this issue too muddled for clarity: The replacement issue is #4590

[angieyan]

@t-will-gillis at the end of the comments on #2652 issue you can see that Justin asked me if I could take #2032 issue, so I assigned this issue to me :)

[t-will-gillis]

@angieyan yes he did! I see that now. We have had others picking up issues from the wrong column before and I made a bad assumption. My apologies!!!

I closed this issue and opened #4590 as a replacement- if you want to grab this one instead and make whatever changes as you see fit, I promise not to get in your way! Thank you for letting me know and apologies again...

[angieyan]

@t-will-gillis no worries :) Apologies accepted, but you need to help me understand how to test the action :)