project: automate issue fields

[evankanderson]

@dussab wanted some housekeeping on GitHub issues, and I'm never gonna remember on my own:

• When an issue is moved to "In Progress", set the "start date"
• When an issues is marked "Done" or moved to the "Done" column, set "end date".

From https://docs.github.com/en/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management#when-do-workflows-run

Many workflow triggers are useful for automating project management.

• An issue is opened, assigned, or labeled.
• A comment is added to an issue.
• A project card is created or moved.
• A scheduled time.

[lukehinds]

This would be really cool

I don't think its relevant to this thread, as we are not dealing with pull requests as the initiating event, but I hit some issues with the github label action and forks: pascalgn/size-label-action#33. - It is possible to work around, but iirc it required elevating to the token permissions, which would give a fork write permissions on the repo.

[evankanderson]

Yeah, this shouldn't apply to forks at all, since they have their own independent issues collection.

[rdimitrov]

@dussab - hey, can we close this or it is this still relevant?

[dussab]

Let's close the issue and we can figure out what type of automation we need once we separate Epics from the mediator repo