Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a PR template for the website #3936

Open
varodrig opened this issue Dec 1, 2024 · 5 comments
Open

Create a PR template for the website #3936

varodrig opened this issue Dec 1, 2024 · 5 comments

Comments

@varodrig
Copy link
Contributor

varodrig commented Dec 1, 2024

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
Copy link
Contributor Author

varodrig commented Dec 1, 2024

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

@hbelmiro
Copy link
Contributor

hbelmiro commented Dec 2, 2024

Sounds good to me.
I think Andrey is enough.

@andreyvelich
Copy link
Member

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
Copy link
Contributor

hbelmiro commented Dec 2, 2024

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
Copy link
Member

andreyvelich commented Dec 2, 2024

General makes sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants