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

REQUEST: New membership for droctothorpe #656

Closed
droctothorpe opened this issue Feb 27, 2024 · 2 comments · Fixed by #657
Closed

REQUEST: New membership for droctothorpe #656

droctothorpe opened this issue Feb 27, 2024 · 2 comments · Fixed by #657

Comments

@droctothorpe
Copy link
Contributor

/kind area/process

Please read the guide lines for joining the Kubeflow GitHub org before opening an issue

Please provide links to PRs or other contributions (2-3):

** Please list 2 existing members who are sponsoring your membership:**
@connor-mccarthy
@andreyvelich

** Please test your PR **

Run

cd github_orgs
pytest test_org_yaml.py

Include the output in the PR

===================================================================================== test session starts =====================================================================================
platform darwin -- Python 3.11.4, pytest-7.4.3, pluggy-1.0.0
rootdir: /Users/inn487/code/kubeflow/internal-acls/github-orgs
plugins: anyio-4.0.0, cov-4.1.0
collected 1 item

test_org_yaml.py .                                                                                                                                                                      [100%]

====================================================================================== 1 passed in 0.11s ======================================================================================

Additional Instructions

After your PR is merged please wait at least 1 hour for changes to propogate.

If after an hour you haven't recieved an invite to join the GitHub org please open an issue.

You can contact build copy in #buildcop in kubeflow.slack.com

Copy link

@droctothorpe: The label(s) kind/area/process cannot be applied, because the repository doesn't have them.

In response to this:

/kind area/process

Please read the guide lines for joining the Kubeflow GitHub org before opening an issue

Please provide links to PRs or other contributions (2-3):

** Please list 2 existing members who are sponsoring your membership:**
@connor-mccarthy
@andreyvelich

** Please test your PR **

Run

cd github_orgs
pytest test_org_yaml.py

Include the output in the PR

===================================================================================== test session starts =====================================================================================
platform darwin -- Python 3.11.4, pytest-7.4.3, pluggy-1.0.0
rootdir: /Users/inn487/code/kubeflow/internal-acls/github-orgs
plugins: anyio-4.0.0, cov-4.1.0
collected 1 item

test_org_yaml.py .                                                                                                                                                                      [100%]

====================================================================================== 1 passed in 0.11s ======================================================================================

Additional Instructions

After your PR is merged please wait at least 1 hour for changes to propogate.

If after an hour you haven't recieved an invite to join the GitHub org please open an issue.

You can contact build copy in #buildcop in kubeflow.slack.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@droctothorpe
Copy link
Contributor Author

droctothorpe commented Feb 27, 2024

Hm the instructions here in the community repo and the readme in this repo diverge from the instructions here on the website. Betting the website is a more reliable source of truth given the various errors in this issue template so closing this issue and filing a PR per its instructions. We may want to bring the two into alignment.

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

Successfully merging a pull request may close this issue.

1 participant