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]

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.

[achingbrain]

Adding the pr template looks good, but there are a bunch of unrelated changes here too?

Adding the stale.yml workflow and changing the secret scanning rules on some non-helia repos?

[whizzzkid]

@achingbrain Interesting, I only added 7dd2a90 then a sneaky commit shows up as me: 82363f8

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 libp2p/github-mgmt#198.

Similarly to that case, here, #181 was left unattended for a while.

I filed an issue for commits that are incorrectly associated with real users - ipdxco/github-as-code#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.

[galargh]

FYI, after this is merged, a new PR actually adding the template to all helia repos will get created.

[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 - ipfs/helia#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?

addressed

[lidel]

Resolved conflicts, merging.