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

feat: Introduce "Welcome" message for new PRs #4644

Merged
merged 8 commits into from
Jun 6, 2023
Merged

Conversation

tomkerkhove
Copy link
Member

Introduce "Welcome" message for new PRs for which we will provide guidance going forward. (more content in follow-up PR.

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to #4640

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
@tomkerkhove tomkerkhove requested a review from a team as a code owner June 4, 2023 21:44
@github-actions
Copy link

github-actions bot commented Jun 4, 2023

Thank you for your contribution! 🙏 We will review it as soon as possible.

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Copy link
Member

@zroubalik zroubalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this really provide any additional value? It's it just more noise on the PR?

@tomkerkhove
Copy link
Member Author

The goal is to add more links that give pointers to dev guide, how to fix DCO, etc but I didn't want to do it all in one PR but happy to do so if you prefer

@zroubalik
Copy link
Member

That kind of information would be beneficial indeed. I would prefer if you can include more information into the initial PR. The current state is just a noise in my opinion 😄

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
@tomkerkhove
Copy link
Member Author

Updated PR with some basic info:
image

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Copy link
Member

@zroubalik zroubalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that it would be better to put more specific stuff, that we usually check. Instead of generic contribution guidelines (which are good in general).

  • Short sentence notifying users to don't forget to add Changelog entry - in alphabetical order
  • Make sure the PR has attached issue & linked in the Changelog
  • Reminding users to check the status of GH Actions/workflows and fix if there's a problem.
  • How to fix the DCO check

I would skip the create new scaler item, we got much more PRs fixing/adding random stuff, new scalers are really a minority of PRs.

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Copy link
Member

@zroubalik zroubalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good!

@tomkerkhove tomkerkhove merged commit 80c4e6a into main Jun 6, 2023
@tomkerkhove tomkerkhove deleted the welcome-message-pr branch June 6, 2023 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants