chore: ➕ Add pull_request_template to all helia* repos.

[whizzzkid]

Summary

Adding pull request template for all helia* projects.

Why do you need this?

For the sake of consistency

DRI: myself

Reviewer's Checklist

• [ ] It is clear where the request is coming from (if unsure, ask)
• [ ] All the automated checks passed
• [ ] The YAML changes reflect the summary of the request
• [ ] The Terraform plan posted as a comment reflects the summary of the request

[github-actions[bot]]

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

ipfs

``` No changes. Your infrastructure matches the configuration. Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed. ```

[whizzzkid]

@achingbrain Interesting, I only added https://github.com/ipfs/github-mgmt/pull/182/commits/7dd2a9060b01d7f9dacd1d88ea2f5bbe6ca8d8e6 then a sneaky commit shows up as me: https://github.com/ipfs/github-mgmt/pull/182/commits/82363f83968e27c706ed27bb19e0de839cef1723

It's unverified, not me, the bot-overlords assumed my identity and pulled these shenanigans.

[achingbrain]

Huh, weird - something similar happened in the libp2p/github-mgmt repo the other day.

@galargh @laurentsenta can this be prevented from happening?

[galargh]

I wrote down a longer reply in https://github.com/libp2p/github-mgmt/pull/198/#discussion_r1440325493.

Similarly to that case, here, https://github.com/ipfs/github-mgmt/pull/181 was left unattended for a while.

I filed an issue for commits that are incorrectly associated with real users - https://github.com/ipdxco/github-as-code/issues/110

As for changing the existing behaviour, you could remove the pull_request_target trigger from https://github.com/ipfs/github-mgmt/blob/master/.github/workflows/fix.yml#L4. Without it, the fix workflow would only get triggered on pushes to the default branch.

[achingbrain]

I'm about to archive most of the @helia/* repos as we're merging them into the main monorepo so this should probably be reduced in scope - https://github.com/ipfs/helia/pull/363

[whizzzkid]

@achingbrain so this should still be merged? Or should wait for the monorepo change? IIUC this can go in independent of that change.

[achingbrain]

I would very much like no further commits to be pushed to the repos that are being merged into the main Helia monorepo.

[whizzzkid]

Alright! @achingbrain I'll merge it once you're ready!

Edit: the merge is blocked on your review. Will merge when unblocked

[achingbrain]

This should be good to go now!

[galargh]

I ran https://github.com/ipfs/github-mgmt/actions/workflows/sync.yml to pull in the repo archivisation actions into the state of this repository.

[SgtPooki]

@lidel @achingbrain do either of you have merge permissions on this?