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

We need automatic labels indicating whether an issue/PR is internal/external. #207

Closed
Ark-kun opened this issue Nov 12, 2018 · 3 comments
Closed

Comments

@Ark-kun
Copy link
Contributor

Ark-kun commented Nov 12, 2018

No description provided.

@vicaire vicaire assigned Ark-kun and unassigned vicaire Nov 12, 2018
@vicaire
Copy link
Contributor

vicaire commented Nov 12, 2018

@Ark-kun, do you have an implementation in mind?

@Ark-kun Ark-kun assigned vicaire and unassigned Ark-kun and vicaire Dec 4, 2018
@Ark-kun
Copy link
Contributor Author

Ark-kun commented Dec 4, 2018

@Ark-kun, do you have an implementation in mind?

I think this is usually handled by the bots. It's similar to when the bots add the "need-ok-to-test" label for the external PRs.

@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

I don't think that is something we will support. Resolving.

@vicaire vicaire closed this as completed Mar 26, 2019
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
…_test (kubeflow#207)

* Use cmp to make it easy to see what is broken

* run dep ensure

* make inline

* Revert "run dep ensure"

This reverts commit 621bef98a86c77dd4a8e28e31690f6c5d270279e.

* return diff inline
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
* Update version from 0.1.0 to 0.2.0
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

2 participants