fix: close only assignee PR

[Keyrxng]

Resolves #4

• adds check for PR closures
• adds tests

I think there may be legitimate scenarios where a PR exists cross-repo but I'm unsure about cross-org. But that will likely be the exception rather than the rule, how do you feel about this approach?

for await (const pr of linkedPullRequests) {
    if (pr.author !== author || pr.organization !== currentRepo.owner.login || pr.repository !== currentRepo.name) {
      continue;

QA: ubq-testing#2 (comment)

• I have two opened PRs one by this account, one by my testing account and the timeline contains PRs from this repo. The comment shows only this account's PR being closed.

[github-actions]

Unused files (2)

src/main.ts, src/plugin.ts

Unused dependencies (2)

Filename	dependencies
package.json	@actions/core @actions/github

Unused exports (1)

Filename	exports
src/types/plugin-input.ts	startStopSettingsValidator

Unused types (1)

Filename	types
src/types/plugin-input.ts	PluginInputs

[0x4007]

I think there may be legitimate scenarios where a PR exists cross-repo but I'm unsure about cross-org. But that will likely be the exception rather than the rule

Ideally we should have support for all the above scenarios. Cross org indeed is rare. If its too complicated then perhaps we can make a new task for it (if needed in the future.)

[Keyrxng]

Cross org indeed is rare. If its too complicated then perhaps we can make a new task for it (if needed in the future.)

I think a new task if required is the way to go.

Correct me if I'm wrong, but for cross-org closures we'd need the bot to be installed in the other org right? I'm assuming based on the earlier attempts of my bot to close #1 and it never succeeding

[Keyrxng]

I want to add that even with the example in the PR body it would still likely be possible for a PR to be closed in error within the same repo depending on what is being cross-referenced

until it's live-tested I can't be sure how effective it's going to be. We are making assumptions about what is being cross-referenced in production and I know there's a good chance it'll close a PR in error eventually with cross-repo closures.

---

I was thinking parse each linked PR body and you'd expect to find a Resolves|Requires # which seems like a good source of truth but I don't think it's infallible either

[Keyrxng]

I've added the PR body check

I referenced the issue from another repo from both an issue and PR. And I couldn't find either of those references in the timeline pre-filtering, which is odd right because previously it was showing PRs between this org and mine.

The sooner we see it live QA-d the better and I'm happy to handle any fixes/tweaks that are needed

fresh QA:

ubq-testing#5

[0x4007]

After my comments are addressed I'm okay to merge.

[Keyrxng]

just double checking that we are good to merge here

[gentlementlegen]

@Keyrxng Yes, the merge issue is unrelated to this and will be addressed within the kernel. I am fine with this pull-request.