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

feature: emit both email and name #96

Open
jaraco opened this issue May 2, 2024 · 5 comments
Open

feature: emit both email and name #96

jaraco opened this issue May 2, 2024 · 5 comments

Comments

@jaraco
Copy link

jaraco commented May 2, 2024

Today, I was working to leverage git-fame to infer the "Authors" and "Maintainers" of a project (contributors). For these fields, I'd like to have both the email and name of these contributors. When I went to invoke git-fame, however, I see that it will emit the name or the email but not both. I've hacked together this monstrosity to zip those together, but it would be so much nicer to get the name and email in one go.

Would you consider an option to include both email and name in the output?

@killi199
Copy link

Unfortunately, I think your code is also not working. It is possible that the number of rows in each output is different. For example, I have this problem with the matplotlib repo. The output of the Table with names contains 33 more rows than the table with emails. I would also like an option to print both name and email in one table.

@jaraco
Copy link
Author

jaraco commented May 17, 2024

Oh, gosh. Yeah, I was making that assumption. Fortunately, that assumption has held for the trivial repos against which I'm relying on it currently, but it'll surely break when that's not the case. Thanks for the heads up.

@jaraco
Copy link
Author

jaraco commented Aug 20, 2024

@casperdcl Would you care to comment on this request?

@casperdcl
Copy link
Owner

I didn't implement this because I knew it would be difficult to safely handle complex cases lacking a comprehensive .mailmap... happy to accept a PR though!

@jaraco
Copy link
Author

jaraco commented Dec 24, 2024

I didn't implement this because I knew it would be difficult to safely handle complex cases lacking a comprehensive .mailmap... happy to accept a PR though!

I'd be interested in exploring the issue or even sponsoring the work, but I'm a little uneasy investing into a project that's shown signs of abandonment, and where I might get a response once or twice a year. What can I do to ensure that any proposed changes aren't stalled by limited bandwidth of the maintainer?

(to be sure, I also have very limited bandwidth for open source, so I'm not complaining; I'm merely seeking clarity on what to expect with this project with respect to a feature change)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants