Github integration is not run when printing context (`--context`) about git-cliff HOT 8 CLOSED

I guess we can add another check where if the remote is configured we activate the integration also. That will likely solve your case as well since no modification on templates are needed. How does it sound?

That sounds perfect!

from git-cliff.

Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️

from git-cliff.

Hey, are you using GitHub related fields (e.g. github.contributors) in your cliff.toml? GitHub data is not fetched as default as long as it is activated via config.

I tried the following and it worked fine:

git cliff --context -c github

from git-cliff.

Hey, are you using GitHub related fields (e.g. github.contributors) in your cliff.toml? GitHub data is not fetched as default as long as it is activated via config.

Do I understand it right that I have to use those fields in my templates or else they won't be fetched? Currently I'm using commit.github.username and the context (printed with --context) looks fine 🤷

from git-cliff.

Yup, that's correct.

from git-cliff.

I see. The line of thought that led me here was that I configured the integration, then I wanted to check if it works by printing out the context and found that it was empty because I haven't touched the templates yet.

Also after #657 is implemented, I believe that users may want to do git-cliff -x and then use the github-related context fields in an external filter.

from git-cliff.

I guess we can add another check where if the remote is configured we activate the integration also. That will likely solve your case as well since no modification on templates are needed. How does it sound?

from git-cliff.

Implemented in #782, any chance that you can check it out locally? 😊

from git-cliff.