issue (git-changelog): changelog didn't show correct user avatar and hyperlink like the example page

[SnowCutieOwO]

Problem described in title.

I'm using Node 20 LTS (both dev preview & build deploy).

It just showed Gravatar generated, not the same one I'm using.
Meanwhile when the example pages could connect contributor name with their github profile, my pages couldn't.

Any ask for extra information is welcomed :3

[Ampernic]

hello

do you use automatic generation or create the schema manually?

Just for automatic, there is a nuance that the mail in git config and the author's main mail on github must match, otherwise it may not display information because it cannot match users.

(this is only my observation during the time of using the integration on ALTGnome projects, I do not claim to be true because I have not fully researched the user matching algorithm)

Can you give more info about integration usage or repo url?

[SnowCutieOwO]

hello

do you use automatic generation or create the schema manually?

Just for automatic, there is a nuance that the mail in git config and the author's main mail on github must match, otherwise it may not display information because it cannot match users.

(this is only my observation during the time of using the integration on ALTGnome projects, I do not claim to be true because I have not fully researched the user matching algorithm)

Can you give more info about integration usage or repo url?

ummm.... i cannot understand some of your words, like schema. i just imported the script and let all other things generated automatically.

the situation is, the git config is correct and i could see myself in commit history, and i believe i'm using same email both for github and git config.

the repo is https://github.com/SnowCutieOwO/snowcutieowo.github.io

[northword]

https://nolebase-integrations.ayaka.io/pages/en/integrations/vitepress-plugin-git-changelog/configure-vite-plugins#option-mapauthors-map-contributors-information

you may need add mapAuthors option in GitChangelog plugin, and add your username to mapAuthor.

example:

integrations/docs/vite.config.ts

Lines 66 to 87 in e620578

	mapAuthors: [
	{
	name: 'Neko',
	username: 'nekomeowww',
	mapByNameAliases: ['Neko Ayaka', 'Ayaka Neko'],
	mapByEmailAliases: ['neko@ayaka.moe'],
	},
	{
	name: 'Rizumu',
	username: 'LittleSound',
	mapByNameAliases: ['Rizumu Ayaka', 'Ayaka Rizumu'],
	mapByEmailAliases: ['rizumu@ayaka.moe'],
	},
	{
	name: 'Nisekoi5',
	username: 'Nisekoi5',
	},
	{
	name: 'Northword',
	username: 'northword',
	},
	],

[SnowCutieOwO]

https://nolebase-integrations.ayaka.io/pages/en/integrations/vitepress-plugin-git-changelog/configure-vite-plugins#option-mapauthors-map-contributors-information

you may need add mapAuthors option in GitChangelog plugin, and add your username to mapAuthor.

example:

integrations/docs/vite.config.ts

Lines 66 to 87 in e620578
mapAuthors: [
{
name: 'Neko',
username: 'nekomeowww',
mapByNameAliases: ['Neko Ayaka', 'Ayaka Neko'],
mapByEmailAliases: ['neko@ayaka.moe'],
},
{
name: 'Rizumu',
username: 'LittleSound',
mapByNameAliases: ['Rizumu Ayaka', 'Ayaka Rizumu'],
mapByEmailAliases: ['rizumu@ayaka.moe'],
},
{
name: 'Nisekoi5',
username: 'Nisekoi5',
},
{
name: 'Northword',
username: 'northword',
},
],

at first i thought it was automatically done. however thanks! :3

[Ampernic]

https://nolebase-integrations.ayaka.io/pages/en/integrations/vitepress-plugin-git-changelog/configure-vite-plugins#option-mapauthors-map-contributors-information

you may need add mapAuthors option in GitChangelog plugin, and add your username to mapAuthor.

example:

integrations/docs/vite.config.ts

Lines 66 to 87 in e620578
mapAuthors: [
{
name: 'Neko',
username: 'nekomeowww',
mapByNameAliases: ['Neko Ayaka', 'Ayaka Neko'],
mapByEmailAliases: ['neko@ayaka.moe'],
},
{
name: 'Rizumu',
username: 'LittleSound',
mapByNameAliases: ['Rizumu Ayaka', 'Ayaka Rizumu'],
mapByEmailAliases: ['rizumu@ayaka.moe'],
},
{
name: 'Nisekoi5',
username: 'Nisekoi5',
},
{
name: 'Northword',
username: 'northword',
},
],

Yes, but this behavior is unexpected. I use this approach for the same reason, but in our case, names often vary, and the overall use case is different. However, in this situation, it's straightforward: there's an author, an avatar, matching nicknames, and correct addresses, but the matching fails, which is strange...

integrations/packages/vitepress-plugin-git-changelog/src/client/composables/changelog.ts

Line 69 in e620578

...gitChangelog.value.authors.find(item => item.name === a.name) ?? {

[SnowCutieOwO]

https://nolebase-integrations.ayaka.io/pages/en/integrations/vitepress-plugin-git-changelog/configure-vite-plugins#option-mapauthors-map-contributors-information
you may need add mapAuthors option in GitChangelog plugin, and add your username to mapAuthor.
example:
integrations/docs/vite.config.ts
Lines 66 to 87 in e620578
mapAuthors: [
{
name: 'Neko',
username: 'nekomeowww',
mapByNameAliases: ['Neko Ayaka', 'Ayaka Neko'],
mapByEmailAliases: ['neko@ayaka.moe'],
},
{
name: 'Rizumu',
username: 'LittleSound',
mapByNameAliases: ['Rizumu Ayaka', 'Ayaka Rizumu'],
mapByEmailAliases: ['rizumu@ayaka.moe'],
},
{
name: 'Nisekoi5',
username: 'Nisekoi5',
},
{
name: 'Northword',
username: 'northword',
},
],

Yes, but this behavior is unexpected. I use this approach for the same reason, but in our case, names often vary, and the overall use case is different. However, in this situation, it's straightforward: there's an author, an avatar, matching nicknames, and correct addresses, but the matching fails, which is strange...

integrations/packages/vitepress-plugin-git-changelog/src/client/composables/changelog.ts

Line 69 in e620578
...gitChangelog.value.authors.find(item => item.name === a.name) ?? {

can we expect this to be fixed in their announcement issue of re-code? :3

[northword]

Currently, only contributor email addresses of the form 000000+username@no-reply.github.com are automatically resolved to GitHub avatars, the rest require mapAuthor to be configured.

@nekomeowww Do you think we could add an option to force contributor avatars to resolve to the Git provider?

[Ampernic]

Currently, only contributor email addresses of the form 000000+username@no-reply.github.com are automatically resolved to GitHub avatars, the rest require mapAuthor to be configured.

@nekomeowww Do you think we could add an option to force contributor avatars to resolve to the Git provider?

Tomorrow is one of my university exams, but after that, I will have some free time. This problem is also relevant to me, as I have worked a bit on the code for this integration, so I believe I can contribute to finding a solution.

[northword]

Yes, but this behavior is unexpected. I use this approach for the same reason, but in our case, names often vary, and the overall use case is different. However, in this situation, it's straightforward: there's an author, an avatar, matching nicknames, and correct addresses, but the matching fails, which is strange...

integrations/packages/vitepress-plugin-git-changelog/src/client/composables/changelog.ts

Line 69 in e620578

...gitChangelog.value.authors.find(item => item.name === a.name) ?? {

emm, could you elaborate on your failed examples and expected examples (in your spare time, of course)?

Also, any ideas or suggestions for a refactored version of #499 are welcome.

[Ampernic]

Also, any ideas or suggestions for a refactored version of #499 are welcome.

Wow, I even missed an opportunity to refactor some code because of my busy schedule.

About my examples - manually creating user records is a pain when there are a lot of people coming to the project.

To solve this issue, we implemented a solution that generates an author map using the GitHub API. We also need this map for an automatically updated page with project participants. However, I think this might be a problem for other projects as well. Implementing something similar out-of-the-box would be a great solution.

Here is an example of a manual map used for replacement.
https://github.com/OlegShchavelev/ALTGnomeWiki/blob/main/_data/team.ts
These are only people whose fields need to be changed and not those taken from GitHub.
You can see the final result on the page: https://alt-gnome.wiki/contributions.html. (There are a lot more of them in the final form, the rest are generated automatically.)