Skip to content

History / How to Test Major Changes to CSS

Revisions

  • fix(test-major-changes-to-css): clarify when to use `npm ci` and `git submodule update`

    @wesleyboar wesleyboar committed Apr 28, 2022
    9be28d1

  • fix(test-major-changes-to-css): better commands and formatting

    @wesleyboar wesleyboar committed Apr 28, 2022
    8c2b586

  • fix(test-major-changes-to-css): clarify output could be identical or similar

    @wesleyboar wesleyboar committed Apr 28, 2022
    9782559

  • fix(test-major-changes-to-css): this → new

    @wesleyboar wesleyboar committed Apr 28, 2022
    3c01658

  • fix(test-major-changes-to-css): genericize wording

    @wesleyboar wesleyboar committed Apr 28, 2022
    b7d0625

  • fix(test-major-changes-to-css): buid → build

    @wesleyboar wesleyboar committed Apr 28, 2022
    16c6955

  • chore(test-major-changes-to-css): `main` → **default**

    @wesleyboar wesleyboar committed Apr 28, 2022
    622949a

  • fix: formatting and main→default

    @wesleyboar wesleyboar committed Apr 28, 2022
    c3487e5

  • fix: add missing footnote to major css change test page

    @wesleyboar wesleyboar committed Apr 28, 2022
    fb5acfd

  • feat(page): How to Test Major Changes to CSS

    @wesleyboar wesleyboar committed Apr 28, 2022
    c55fdec