Built-in Github cookie, managed by the cookie consent manager.

[white-gorilla]

Hello,

Sorry, that's probably a beginner's question.

I have activated GA4 on our website and the cookie consent manager.
Everything works perfectly. The two GA cookies are created well, or not, depending on his choice. The tracking in GA works fine.

My question is about the built-in Github cookie, which is enabled by default. I don't understand what it does (github cookies are created if GA4 cookies are not allowed, and replaced by those of GA4 if it is activated. In any case, I don't see any queries or anything sent if Github cookies are enabled).

Can you help me?

Thanks in advance.

Vincent.

[squidfunk]

The GitHub "cookie" is needed for consenting to request repository statistics from GitHub (top right). There's not really a cookie set, as it's just Material for MkDocs performing two requests against GitHub's API. It was pointed out in #4329 that the application performed these request without the user's prior consent, so when you enable the cookie consent, and have a GitHub repository configured, the consent needs to be given by the user. The GitHub cookie will be automatically added:

mkdocs-material/src/partials/consent.html

Lines 30 to 34 in 13655d6

	{% if config.repo_url and "github.com" in config.repo_url %}
	{% if "github" not in cookies %}
	{% set _ = cookies.update({ "github": "GitHub" }) %}
	{% endif %}
	{% endif %}

If this is not the case, please create an issue with a minimal reproduction that showcases the issue.

[white-gorilla]

Thank you very much @squidfunk for this very clear answer. It's OK with me.