-
Notifications
You must be signed in to change notification settings - Fork 210
Add Irene as contributor #1191
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
base: main
Are you sure you want to change the base?
Add Irene as contributor #1191
Conversation
thank you for this pr. Could you please add a short description why you like to join and sign the EasyCLA which is a prerequisite to approve the pr. |
Hi @beyhan, Regarding the EasyCLA signing, I'm currently in the process of getting internal approval to be certified as part of Broadcom in this tool. I'll let you know as soon as that's done. Thank you so much for your attention and support. |
hi @beyhan , just letting you know that I was finally able to sign the easyCLA. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, Irene will be joining the team
Ok, then we nee two approvals from the @cloudfoundry/wg-foundational-infrastructure-identity-and-auth-uaa-approvers as defined in our https://github.com/cloudfoundry/community/blob/main/toc/ROLES.md?plain=1#L512-L533 and WG leads can merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Irene is joining the team.
could you please rebase your fork on the latest community repository main branch. There should be a conflict which is not shown in the UI. I tried to change the base branch and then back which should help as discussed here but it didn't. Rebasing on latest main branch will also solve the failing check. |
No description provided.