Issue template workspace dropdown

[kurtaking]

Hey, I just made a Pull Request!

A start at solving for #2507.

I identified issue templates don't allow for importing from other yaml files. So, we would need to keep the dropdown up-to-date in each template.

• refactor functionality to list workspaces to dedicated helper function list-workspaces.js
• refactor existing scripts to use listWorkspaces()
• add create-workspaces-dropdown.js to generate the yaml dropdown

Testing

• ran each script locally after refactor

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)
• All your commits have a Signed-off-by line in the message. (more info)

[kurtaking]

Soliciting feedback on whether or not it would be worth maintaining the dropdown list manually. Perhaps, trying to add a label based on the user's input in the issue, even if it occasionally doesn't work due to typos, may outweigh maintaining the dropdown list in each issue.

[04kash]

Could we have another script to rewrite the whole ISSUE_TEMPLATE (I think the only ones where we'd want to use the drop down are: 1-bug.yaml and 2-feature.yaml) with the updated workspaces? We could have a cron job to run this script periodically.

[kurtaking]

Could we have another script to rewrite the whole ISSUE_TEMPLATE (I think the only ones where we'd want to use the drop down are: 1-bug.yaml and 2-feature.yaml) with the updated workspaces? We could have a cron job to run this script periodically.

I like the idea, and it's doable. I'll work on it more and then ping you.

[kurtaking]

todo:

• what is the best way to test this action?
• should probably improve the output logging

[kurtaking]

Hey @04kash - made some progress here and could use a review.