Skip to content

Conversation

@kramaranya
Copy link
Contributor

I added a CI to write a comment to the PRs from new contributors. I'm using https://github.com/actions/first-interaction
An example of this GH action is google/blockly#9250 (review)

I borrowed this idea from Model Registry, thanks @tarilabs!

cc @kubeflow/kubeflow-sdk-team

Signed-off-by: kramaranya <kramaranya15@gmail.com>
@coveralls
Copy link

coveralls commented Sep 2, 2025

Pull Request Test Coverage Report for Build 17445598990

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 73 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+5.1%) to 70.146%

Files with Coverage Reduction New Missed Lines %
kubeflow/trainer/backends/kubernetes/backend.py 17 78.1%
kubeflow/trainer/utils/utils.py 56 61.88%
Totals Coverage Status
Change from base Build 17382047367: 5.1%
Covered Lines: 289
Relevant Lines: 412

💛 - Coveralls

Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

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

That's great idea, thank you for this @kramaranya!
We should also add this for Kubeflow Trainer.
cc @kubeflow/kubeflow-trainer-team @kubeflow/kubeflow-sdk-team @kubeflow/wg-training-leads

Thanks for opening your first PR! We're happy to have you as part of our community 🚀

**Here's what happens next:**

Copy link
Member

Choose a reason for hiding this comment

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

Maybe it worths to also link the Kubeflow contributor guide, since it explains that commits must be singed: https://www.kubeflow.org/docs/about/contributing/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, let me add this


**Here's what happens next:**

- If you haven't already, please check out our [Contributing Guide](https://github.com/kubeflow/sdk/blob/main/CONTRIBUTING.md)
Copy link
Member

Choose a reason for hiding this comment

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

Shall we also encourage them to join Kubeflow Slack channels (e.g. #kubeflow-trainer and #kubeflow-ml-experience) and community calls ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, I'll update it!
However I think we should just refer to #kubeflow-ml-experience, wdyt?

Copy link
Member

Choose a reason for hiding this comment

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

From my point of view, it would be beneficial for contributors to join both of these channels, since Kubeflow SDK will affect many Kubeflow projects.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, but in this case will we need to also add Slack channels for model registry, pipelines, katib etc?

Copy link
Member

Choose a reason for hiding this comment

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

Let's add them once we support it in Kubeflow SDK ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I meant do we actually want to explicitly point to each project's slack channel? If we list multiple channels, it might confuse new contributors about where to start or which channel to use for what.

I'll add trainer to the list, but in the future (same in README) maybe we could point to #kubeflow-ml-experience as the primary channel and add a note that contributors should also join other project specific channels (like trainer, pipelines) if they're working on features that touch those components?

Copy link
Member

Choose a reason for hiding this comment

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

Sure, we can do that.

If they're working on features that touch those components?

In any case, contributors will work on features that touch some Kubeflow sub-projects, so they should be aware of the development.

permissions:
pull-requests: write
steps:
- uses: actions/first-interaction@v3
Copy link
Member

Choose a reason for hiding this comment

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

Do you know how it detects the first interaction ? Does it check how many PRs user opens ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know for sure, I think it just checks whether the PR author has ever opened a PR here before https://github.com/actions/first-interaction/tree/main?tab=readme-ov-file#first-interaction
and just hope it'll work... :)

Signed-off-by: kramaranya <kramaranya15@gmail.com>
@google-oss-prow google-oss-prow bot added size/M and removed size/S labels Sep 3, 2025
Signed-off-by: kramaranya <kramaranya15@gmail.com>
Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

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

Thank you @kramaranya!
If you can create similar action in KF Trainer, that would be great!
/lgtm
/assign @kubeflow/kubeflow-sdk-team

@kramaranya
Copy link
Contributor Author

If you can create similar action in KF Trainer, that would be great!

Sure, I will! Let's just first ensure it works :)

Copy link
Member

@Electronic-Waste Electronic-Waste left a comment

Choose a reason for hiding this comment

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

@kramaranya Thanks for this great contribution. LGTM!

/lgtm

Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

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

/approve

@google-oss-prow
Copy link

[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:

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

@google-oss-prow google-oss-prow bot merged commit d5c60f5 into kubeflow:main Sep 7, 2025
10 checks passed
@google-oss-prow google-oss-prow bot added this to the v0.1 milestone Sep 7, 2025
accorvin pushed a commit to opendatahub-io/kubeflow-sdk that referenced this pull request Oct 8, 2025
* chore: Add welcome new contributors CI

Signed-off-by: kramaranya <kramaranya15@gmail.com>

* Add community links to welcome CI

Signed-off-by: kramaranya <kramaranya15@gmail.com>

* Add slack channels to CI

Signed-off-by: kramaranya <kramaranya15@gmail.com>

---------

Signed-off-by: kramaranya <kramaranya15@gmail.com>
MStokluska pushed a commit to opendatahub-io/kubeflow-sdk that referenced this pull request Oct 15, 2025
* chore: Add welcome new contributors CI

Signed-off-by: kramaranya <kramaranya15@gmail.com>

* Add community links to welcome CI

Signed-off-by: kramaranya <kramaranya15@gmail.com>

* Add slack channels to CI

Signed-off-by: kramaranya <kramaranya15@gmail.com>

---------

Signed-off-by: kramaranya <kramaranya15@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants