-
-
Notifications
You must be signed in to change notification settings - Fork 670
new CI issues #863
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
Comments
Ah, I've made the check non-optional in the workflow to check what happens. I guess if the email isn't public on ones GitHub profile, this is what happens. Two ways to deal with it: Either make it optional again, but not sure how useful it is then, or require contributors to have a public email address. |
Well-actually-ing myself: I have a different email address as my public one, but it still works. So it might also be a Git configuration issue of the kind
|
I tried exactly that, but I can try to make my email address public. |
I ran into an issue with this check when I created #919. I have two email addresses in GitHub: one Gmail and one personal domain. I created the commit with my personal domain address, but the NOTICE check had an error because it couldn't find my Gmail address. I added a To get around the issue, I changed my primary to my personal domain address, but maybe this is the root cause of @willemneal's issue. Maybe the check should ignore the merge commit? |
I guess AUTHOR's email in ci could be retrieved using mailmaps via |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I currently have the following error when pushing trying to test the new setup.
I first pushed with gitkraken, which is logged into my github account. But then tried normally and it still didn't like it.
The text was updated successfully, but these errors were encountered: