Skip to content

Add per-column header tooltips shown after the hover dwell delay (v5.… #78

Add per-column header tooltips shown after the hover dwell delay (v5.…

Add per-column header tooltips shown after the hover dwell delay (v5.… #78

Workflow file for this run

name: CI
on:
push:
branches: [master, main]
tags: ["v*.*.*"]
pull_request:
branches: [master, main]
workflow_dispatch:
env:
CARGO_TERM_COLOR: always
jobs:
build:
runs-on: macos-latest
steps:
- uses: actions/checkout@v4
- uses: dtolnay/rust-toolchain@stable
- uses: Swatinem/rust-cache@v2
# `--locked`: CI must test exactly the dependency versions committed in
# Cargo.lock; bumping them is an explicit `cargo update` in a PR.
- name: Check formatting
run: cargo fmt --check
- name: Compile all targets
run: cargo check --locked --all-targets
- name: Clippy
run: cargo clippy --locked --all-targets -- -D warnings
- name: Documentation
run: cargo doc --locked --no-deps
- name: Unit tests
run: cargo test --locked --lib
- name: Integration tests
run: cargo test --locked --test text_box_gpui
# NOTE: no `cargo package` / crates.io publish here (and the tag-triggered
# publish job is intentionally gone). Since the v4.1.1 port to the zed *git*
# gpui API (`Anchor`, `focus(window, cx)`, `TextAlign` paint), the source no
# longer compiles against the registry `gpui = "0.2"` (0.2.2) it declares —
# the workspace-root `[patch.crates-io]` redirects to the git sources for
# every build above, but `cargo package` verifies the isolated crate against
# the registry gpui and fails, and `cargo publish` would upload a crate that
# no registry-gpui consumer could build. This library is consumed downstream
# by git tag (e.g. the SQLLY workspace pins `tag = "v4.1.x"`), not from
# crates.io. Restore the Package/Publish steps only when a registry gpui
# release ships the git API this code targets. Last crates.io release: 4.1.0.