* SQLite - setup in the integration test, where we create a temporary database
file
## Link Checking and Fixing with Lychee
We use **[lychee](https://github.com/lycheeverse/lychee-action)** for repository link checks.
* To run the checker **locally**, see the [command-line usage guide](https://github.com/lycheeverse/lychee?tab=readme-ov-file#commandline-usage).
### Fixing Broken Links
1. **Update the Link:** Correct the broken URL or update the content where it is used.
2. **Ignore the Link:** If you can't fix the link (e.g., due to **external rate-limits** or if it's a **local-only URL**), tell Lychee to **ignore** it.
* List **regular expressions** or **direct links** in the **[.lycheeignore](https://github.com/googleapis/genai-toolbox/blob/main/.lycheeignore)** file, one entry per line.
* **Always add a comment** explaining **why** the link is being skipped to prevent link rot. **Example `.lycheeignore`:**
```text
# These are email addresses, not standard web URLs, and usually cause check failures.
^mailto:.*
```
> [!NOTE]
> **GitHub Action Check**: The link checker runs against the raw Markdown files in the repository structure, treating links as relative file paths (e.g., ../content/page.md).<br>
> **Hugo Server**: The static site generator resolves links based on the final clean URL structure (e.g., /page/) and the configured baseURL.<br>
> **Crucial Difference**: A link that works as a file path for the GitHub Action (e.g., ./image.png) may break in the final HTML generated by Hugo if the URL path is different, and vice-versa. You must ensure your linking strategy—often using root-relative paths (/path/) or Hugo Page Bundles—works seamlessly for both.
### Other GitHub Checks
* License header check (`.github/header-checker-lint.yml`) - Ensures files have
out,err:=testutils.WaitForString(waitCtx,regexp.MustCompile(`Server ready to serve`),cmd.Out)
iferr!=nil{
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.