Issues/PR in Changelogs from GitHub Enterprise Server should point to that Enterprise Server instead of github.com

[Shegox]

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us what version of Renovate you run.

34.41.0

If you're self-hosting Renovate, select which platform you are using.

GitHub Enterprise Server

If you're self-hosting Renovate, tell us what version of the platform you run.

3.5.5

Was this something which used to work for you, and then stopped?

I never saw this working

Describe the bug

When Renovate adds Changelogs from internal packages hosted on GitHub Enterprise Server (GHES) and they only contain references like #16, Renovate leverages the below function to translate them to actual GitHub links.

renovate/lib/util/markdown.ts

Lines 28 to 44 in 4de1df3

	/**
	*
	* @param content content to process
	* @param options github options
	* @returns linkified content
	*/
	export async function linkify(
	content: string,
	options: github.RemarkGithubOptions
	): Promise<string> {
	// https://github.com/syntax-tree/mdast-util-to-markdown#optionsbullet
	const output = await remark()
	.use({ settings: { bullet: '-' } })
	.use(github, { mentionStrong: false, ...options })
	.process(content);
	return output.toString();
	}

Currently these links always point to github.com and not to the hosted GitHub Enterprise Server.

This can be archived with speciying a custom buildUrl in remarkJS.

---

Currently following happens:

A changelog like this

gets transformed to this markdown:

### Release Notes

<details>
<summary>my-org/my-dependency-repo</summary>

### [`v0.4.3`](https://github.enterprise.com/my-org/my-dependency-repo/blob/HEAD/CHANGELOG.md#&#8203;043---2022-12-02)

-   Automate GitHub Releases ([#&#8203;16](https://github.com/my-org/my-dependency-repo/issues/16))

The expected markdown should look like this:

### Release Notes

<details>
<summary>my-org/my-dependency-repo</summary>

### [`v0.4.3`](https://github.enterprise.com/my-org/my-dependency-repo/blob/HEAD/CHANGELOG.md#&#8203;043---2022-12-02)

-   Automate GitHub Releases ([#&#8203;16](https:///github.enterprise.com/my-org/my-dependency-repo/issues/16))

I will create a PR next week to address this.

Relevant debug logs

n/a

Have you created a minimal reproduction repository?

No reproduction repository

[Shegox]

After digging a bit into it, it seems that the baseUrl option to change the GitHub base url requires github-remark v11 (Renovate currently uses github-remark v10). github-remark v11 is distributed as ESM only and therefore can't be used.

Because of that and because I don't see a quick workaround I would put it on hold until ESM support is added in Renovate:

• Publish CJS + ESM #13181
• Migrate from cjs to esm #9890

If we really want to add it now, we could ask if the github-remark project backports the feature to v10 and releases that as commonjs module -or- do that ourself and use a fork of it.

[rarkins]

I'm going to close this as a duplicate of #19503 because I think it's the same problem and that one has a reproduction using gitlab.com

[rarkins]

Duplicate of #19503