Skip to content

Conversation

@asaadbalum
Copy link

When Info/Warning/Danger redirection level:
image

When no BE response:
image

When wrong redirection level:
image

@ederign
Copy link
Member

ederign commented Feb 4, 2025

/assign @paulovmr

@ederign
Copy link
Member

ederign commented Feb 4, 2025

@asaadbalum thanks for the PR! @paulovmr can you please take a look on it?

Meanwhile, @asaadbalum can you fix the PR title for semantic values and also sign the commits (DCO check)?

@asaadbalum
Copy link
Author

@asaadbalum thanks for the PR! @paulovmr can you please take a look on it?

Meanwhile, @asaadbalum can you fix the PR title for semantic values and also sign the commits (DCO check)?

Is if fine now?

Copy link

@paulovmr paulovmr left a comment

Choose a reason for hiding this comment

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

Hi @asaadbalum , to fix the semantic PRs check, your PR title needs to have a prefix following the Conventional commits specification. For notebooks 2.0 tasks, the scope is "ws", a reference to "workspaces". Therefore, the majority of pull request we are sending would have a name like "feat(ws): ". Considering that, if you add the "feat(ws): " prefix to your PR title, it should be fixed.

To fix the DCO check, you need to sign off your commits. There is information here with a few options on how to do it.

Also, everytime before submitting a PR, please consider running npm run test to check for linting and tests errors. Most of the formatting issues can be solved automatically with npm run test:fix.

@asaadbalum asaadbalum changed the title Notebooks 2.0 // Frontend // Workspaces table // Workspace redirect status column #147 feat(ws): Notebooks 2.0 // Frontend // Workspaces table // Workspace redirect status column #147 Feb 6, 2025
@asaadbalum asaadbalum force-pushed the RHOAIENG-16238-2 branch 7 times, most recently from 959de7a to 4c4a104 Compare February 6, 2025 14:11
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ederign, paulovmr

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

@ederign
Copy link
Member

ederign commented Feb 11, 2025

/ok-to-test

@thesuperzapper
Copy link
Member

/ok-to-test

@thesuperzapper
Copy link
Member

/retest

@kubeflow kubeflow deleted a comment from google-oss-prow bot Feb 12, 2025
@thesuperzapper
Copy link
Member

Ok, I have made a PR that should fix the workflows not running for new contributors (as long as the PR has the ok-to-test label):

@paulovmr
Copy link

/lgtm

@google-oss-prow google-oss-prow bot added the lgtm label Feb 12, 2025
@google-oss-prow google-oss-prow bot merged commit f22890d into kubeflow:notebooks-v2 Feb 12, 2025
6 checks passed
Mohamed-ben-khemis pushed a commit to Mohamed-ben-khemis/notebooks that referenced this pull request Mar 13, 2025
mkoushni pushed a commit to mkoushni/notebooks that referenced this pull request May 28, 2025
andyatmiami pushed a commit to andyatmiami/kubeflow-notebooks that referenced this pull request Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants