Files
anki/.github
Luc Mcgrady 73985c7195 docs: ninja build for cog (#4972)
<!--
Title (for the Pull Request title field at the top):
Use a short prefix so the change type is obvious. You do not need to
repeat it in the body below.

Examples:
- fix: — bugfix
- feat: — feature
- refactor: — internal change without user-facing feature
- docs: — documentation only
- chore: — tooling, CI, deps, build housekeeping
- test: — tests only
-->

## Linked issue (required)

<!-- Fixes #123 / Closes #123 / Refs #123 -->
https://github.com/ankitects/anki/pull/4882#discussion_r3370633312

## Summary / motivation (required)

This lets cog run when ./check is run
Github actions are difficult to run locally and its better to have
everything run with a simple ./check command IMO

>       - name: Validate Mintlify docs
>        run: mint validate
>        working-directory: docs-site

Maybe it is better to leave this as a separate action because that way
it wont run when only code is modified and not the docs?

## Steps to reproduce (required, use N/A if not applicable)
N/A

## How to test (required)
Make a change to the `pylib/tools/genhooks.py` file, run ./check and it
should be reflected in mintlify docs.

### Checklist (minimum)

- [ ] I ran `./ninja check` or an equivalent relevant check locally.
- [ ] I added or updated tests when the change is non-trivial or
behavior changed.

### Details

<!-- Commands, manual steps, edge cases, and what you observed -->

## Before / after behavior (optional)

<!-- For bugfixes: behavior before vs after. For other types: N/A or a
short note. -->

## Risk / compatibility / migration (optional)

<!-- Breaking changes, rollout notes, or N/A for small / low-risk PRs
-->

## UI evidence (required for visual changes; otherwise N/A)

<!-- Screenshot or short video -->

## Scope

- [X] This PR is focused on one change (no unrelated edits).

---------

Co-authored-by: Abdo <abdo@abdnh.net>
2026-06-09 20:28:35 +03:00
..
2026-05-05 17:29:18 -04:00