Automatically link issues to their respective PR

[Monstarrrr]

Currently

Whenever we create a PR, we can go to the issue whose PR it was made for and link them, so that when the PR is merged, the issue is automatically closed.

Example

What would be nice to have instead

It would be very helpful to have that automated, but not sure if feasible:

When a PR is created, link the PR to its Issue, and link the Issue to its PR (under the Development category in the sidebar).

[seporterfield]

Tying the lifespan of an issue to a branch would mean we have to be disciplined about the scope of the issues we connect to the PR.

Epics or issues with lots of complex subtasks would never be tied to a PR, otherwise we'd end up with long lived branches and merge hell.

Despite that danger, it seems worth trying--
Particularly since not all issues need to have PRs, they can be closed by completing other smaller issues instead.

[Monstarrrr]

No like, doing it, as we're now in trunk-based, unless you have downsides to its implementation in mind?

[seporterfield]

Yeah but what issue are you referring to? I'm not sure what the task is. What needs to be done?

[Monstarrrr]

When a PR is created, link the PR to its Issue, and link the Issue to its PR (under the Development category in the sidebar).

[seporterfield]

It would take about 10 seconds to do this manually per new pull request.
Being generous, 500 pull requests in the MVP * 10s = 1h23m of toil.

That means an automation would cost more in the long run even if it only takes an hour and a half of maintenance/update time per release life cycle stage.

I'll make the issue to enable fun/learning/experimentation but bump it up a few iterations.

[Monstarrrr]

It's mostly a matter of ensuring we stop forgetting it, but maybe that's still not worth the time, i'd have assumed it's a common action so a solution might exist that only need tiny adjustment 🤷