Fix what? They setup LLM with access to private data and ability to read public comments. That's simply misconfiguration.

▲

wzdd 5 hours ago | parent [-]

The OP notes that they had to use special phrasing to get their exfil to work, so clearly GitHub was aware of the issue and made an attempt to prevent it.

It seems like the proper fix is for GitHub not to allow their agentic workflow to execute in a public repo context if it also has private repo access. Or, to use your phrasing, for GitHub to flag and disallow this easily-detectable and dangerous type of misconfiguration.

	▲	brookst 2 hours ago \| parent [-]
		This “detectable and dangerous type of misconfiguration” is used by many developed daily and breaking it would break important workflows. It’s like saying that an OS should enforce that home directories can only have 0600 permissions. Yes, it prevents accidentally configuring world readable on files, but there are legit reasons for wanting to share a file from your home dir.