Add CI step to create a issue from a PR

[vitorsavian]

Proposed Changes

• New CI step for new PRs

This new CI step will create a issue when someone that is not a public member of k3s.

Types of Changes

• Feature

Verification

• See if you are public in the k3s organization and change to private if you are public

• Create a PR without a link to a GitHub issue in the body of the PR

• Follow to checks and then see the issue created that will be posted in the comments

Testing

Linked Issues

• Investigate github issue creation automation #9272

User-Facing Change

Further Comments

• The team members who write PRs will need to be public on the k3s organization

[dereknola]

Does this handle the existence of existing linked issues (i.e. I already have a linked issue in the PR body when i open the PR)?

[dereknola]

Hiding the logic inside a external action is not super helpful, we should move this within the k3s-org.

[dereknola]

Suggested change

	name: Create issue from PR
	name: Create linked issues for PRs without one

[vitorsavian]

Does this handle the existence of existing linked issues (i.e. I already have a linked issue in the PR body when i open the PR)?

It does not, I remember Caroline saying something about using this to make we track the PRs using the issues

but I believe it can be done, the steps takes then entire body of the PR

[vitorsavian]

Hiding the logic inside a external action is not super helpful, we should move this within the k3s-org.

That is a thing that I want to speak with the team, is it ok to create a new repo to add the js logic?

[vitorsavian]

@dereknola I changed the action to entire shell script within the actions, I think it is better instead of having to build Js inside the .github/actions