Creates a Template for new PRs

[varodrig]

Checklist:

• [x ] You have signed off your commits
• [x ] Ensure you follow best practices from our guide. Contributing.

Description of your changes:
This PR creates a new template for new PRs similar to this description. This will help the community to understand quickly what a PR will be enhancing or resolving in the website. Additionally by linking the issue it helps reduce the issues that are not closed even thought were resolved.

Issue

Closes: #3936

Labels

/area other

[google-oss-prow]

@varodrig: The label(s) area/other cannot be applied, because the repository doesn't have them.

In response to this:

Checklist:

• [x ] You have signed off your commits
• [x ] Ensure you follow best practices from our guide. Contributing.

Description of your changes:
This PR creates a new template for new PRs similar to this description. This will help the community to understand quickly what a PR will be enhancing or resolving in the website. Additionally by linking the issue it helps reduce the issues that are not closed even thought were resolved.

Issue

Closes: #3936

Labels

/area other

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[varodrig]

/area other

[google-oss-prow]

@varodrig: The label(s) area/other cannot be applied, because the repository doesn't have them.

In response to this:

/area other

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[varodrig]

@andreyvelich and @hbelmiro to review thank you and anyone else from the community who wants to provide feedback.
Also we need to create new labels before merging. Can you help with this?
Created an issue
#3967

[varodrig]

/hold

[varodrig]

cc @kubeflow/kubeflow-steering-committee @kubeflow/wg-training-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-manifests-leads @kubeflow/release-team @kubeflow/wg-data-leads @kubeflow/wg-deployment-leads

[hbelmiro]

/lgtm

I'm not allowed to modify labels @varodrig.

[varodrig]

/area website

[varodrig]

/hold cancel

[hbelmiro]

/lgtm

[varodrig]

Since this is affecting all Working groups, please review

@hbelmiro @thesuperzapper @rimolive @tarilabs @franciscojavierarceo

[andreyvelich]

@varodrig Would it be better to ask users to open website-related issues in the corresponding GitHub repositories for each project?

From our past experience, WG leads tend to triage issues more effectively in their own repos than in kubeflow/website.
cc @jbottum

Sorry this message relates to: #3964

[hbelmiro]

/lgtm

[juliusvonkohout]

I am in favor of merging this as soon as possible to have the basic functionality and then iterating on it in follow-up PRs.

[andreyvelich]

@varodrig Can you create tracking issue for the GitHub actions automation so we can find contribution who can work on it?

[andreyvelich]

thank you for this effort @varodrig!
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andreyvelich]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment