Create a PR template for the website

[varodrig]

Create a PR template for the website to required information and pre-reqs are done before PR is submitted.

After reviewing some of the 79 PRs pending, https://github.com/kubeflow/website/pulls , I noticed some PR were missing the commits sign off

Reference:

https://github.com/kubeflow/pipelines/blob/master/.github/pull_request_template.md

[varodrig]

@hbelmiro anyone else to comment on this issue?
@andreyvelich

[hbelmiro]

Sounds good to me.
I think Andrey is enough.

[andreyvelich]

That sounds good to me @varodrig.
Any ideas on how we can design our PR template for contributors ?
Maybe we should ask them to put component name in the PR title. For example:

Training: <Training Operator PR>
Katib: <Katib PR>
Pipelines: <KFP PR>

WDYT @hbelmiro @varodrig ?

[hbelmiro]

I like your idea @andreyvelich.
Also, some PRs don't target any component, like more website-focused PRs. For example, fixing the Kubeflow logo.
In those cases, we can use General. (Any other better idea?)
We could use Website, but I think it may confuse users, like using Website when they should use Pipelines because they are sending a PR to the website.

[andreyvelich]

General makes sense to me.

[varodrig]

/assign @varodrig

[jaiakash]

Here we could add -

• Commit sign-off
• Closes/Fixes Checkbox
• Screenshot
• Owners

One of the good I found is https://github.com/keploy/keploy/blob/main/.github/PULL_REQUEST_TEMPLATE.md

[andreyvelich]

As @varodrig mention, I would suggest that we add the component name into PR title for the website.
That will help to assign correct reviewers for various Kubeflow Components:
For example:

pipelines:
notebooks:
trainer:
katib:
model-registry:
spark-operator:

[jaiakash]

Got it, So for now what i understood is -

PR title

<component name>: <PR explanation>

PR Body

Closes #<issue number>

• I signed off all the commits. See this

<Explanation>

<Screnshots>

[varodrig]

status: PR created on hold till address issue #3967

[varodrig]

/hold