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

update committers list #194

Merged
merged 1 commit into from
Aug 31, 2023
Merged

update committers list #194

merged 1 commit into from
Aug 31, 2023

Conversation

lsf37
Copy link
Member

@lsf37 lsf37 commented Aug 21, 2023

Scott and Zoltan have left UNSW, Rob switched from Melbourne to UNSW, and Indan has accepted the committer role.

@lsf37 lsf37 requested a review from Indanz August 21, 2023 10:18
@lsf37
Copy link
Member Author

lsf37 commented Aug 21, 2023

@Indanz I've assigned the PR to you so you can try out the new rights by merging the PR (if you approve of it).

processes/roles.md Outdated Show resolved Hide resolved
@Indanz
Copy link
Contributor

Indanz commented Aug 21, 2023

I just moved to Ireland and I'm very busy sorting things out here. I'll merge this later this week, after I figured out how to get a local checkout and update this and all that. In the meantime, if anyone else has info that needs updating, please say so.

Scott and Zoltan have left UNSW, Rob switched from Melbourne to UNSW,
Indan has accepted the committer role, and Axel has left Hensoldt.

Signed-off-by: Gerwin Klein <[email protected]>
@Indanz
Copy link
Contributor

Indanz commented Aug 30, 2023

How can I see which email address will be used? I noticed elsewhere that Github still wants to use my MEP email for update with master merges, and I'm afraid it will want to do the same for upstream merges. I can't find how to tell Github to not use my old MEP email for anything other than removing the address altogether.

@axel-h
Copy link
Member

axel-h commented Aug 30, 2023

How can I see which email address will be used?

You mean you github account's e-mail address? See https://github.com/settings/emails
For you local commits, the git settings from ~/.gitconfig are used.

@Indanz
Copy link
Contributor

Indanz commented Aug 30, 2023

I found that page and Github docs say it will use my primary email for actions done via the web interface. However, that doesn't seem to be true, considering it tells me:

"Merge the latest changes from master into this branch.

This merge commit will be associated with [email protected]."

on a PR page, hence my question.

@lsf37
Copy link
Member Author

lsf37 commented Aug 30, 2023

I found that page and Github docs say it will use my primary email for actions done via the web interface. However, that doesn't seem to be true, considering it tells me:

"Merge the latest changes from master into this branch.

This merge commit will be associated with [email protected]."

on a PR page, hence my question.

Strange, for me it does tend to use the primary address. Is there any option on that merge page to use a different address?

@Indanz
Copy link
Contributor

Indanz commented Aug 30, 2023

I can't find any! All I can think of is that it uses my last used signed-off for seL4, even after changing my email settings. I can merge it, but it may have the wrong signed-off line if I do it via the web interface.

@Indanz Indanz merged commit 6eb462f into master Aug 31, 2023
8 checks passed
@Indanz Indanz deleted the indan branch August 31, 2023 16:23
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 this pull request may close these issues.

3 participants