Skip to content

Commit

Permalink
Try to fix several missing favicons in doc (#310)
Browse files Browse the repository at this point in the history 
* try to fix several missing favicons in doc

* fix indent
  • Loading branch information
@ytdHuang
ytdHuang authored Nov 15, 2024
1 parent afded9a commit 9567c45
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions docs/src/.vitepress/config.mts
View file
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,10 @@ export default defineConfig({
cleanUrls: true,
outDir: 'REPLACE_ME_DOCUMENTER_VITEPRESS', // This is required for MarkdownVitepress to work correctly...
head: [
['link', { rel: 'icon', href: 'REPLACE_ME_DOCUMENTER_VITEPRESS_FAVICON' }],
['script', {src: `/QuantumToolbox.jl/versions.js`}],
['script', {src: `${baseTemp.base}siteinfo.js`}]
['link', { rel: 'icon', href: '/QuantumToolbox.jl/favicon.ico' }],
['link', { rel: 'icon', href: 'REPLACE_ME_DOCUMENTER_VITEPRESS_FAVICON' }],
['script', {src: `/QuantumToolbox.jl/versions.js`}],
['script', {src: `${baseTemp.base}siteinfo.js`}]
],
ignoreDeadLinks: true,

Expand Down

2 comments on commit 9567c45

@ytdHuang
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/119474

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.21.5 -m "<description of version>" 9567c45a7a62b7042c02102faa11309e43138fda
git push origin v0.21.5

Please sign in to comment.