Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Add condition to prevent the website preview deployment from running
on PRs from forked repositories, which would fail due to lack of
write permissions to the gh-pages branch.

The condition 'github.event.pull_request.head.repo.full_name == github.repository'
ensures the preview job only runs for PRs from the same repository.

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: azu <azuciao@gmail.com>

Co-authored-by: azu <azu@users.noreply.github.com>

…ig (#1607)

* fix: preserve preset severity settings when user provides partial rule configuration

- Replace nullish coalescing operator with proper object merging in loadPreset function
- Fixes issue where preset severity was lost when users provided partial rule config
- Maintains backward compatibility for boolean configurations
- Add comprehensive unit tests for preset + severity combinations
- Add CLI-level integration tests

Fixes #1606

* remove

* fix remove

* remove

* test: add snapshots test

* fix

* fix

* fix text case

* feat: add support for 'info' severity level in textlint rules and formatters

* feat: implement 'info' severity level handling in stylish and checkstyle formatters

* feat: add support for 'info' severity level in various formatters and tests

* fix: correct stylish formatter test expectation for info severity level

The test was expecting '1 warning' but should expect '1 info' when severity is 3.
This aligns with the actual formatter output that correctly displays info messages.

* refactor: remove @textlint/kernel dependency from formatters

- Replace TextlintRuleSeverityLevelKeys with numeric values (1: warning, 2: error, 3: info)
- Remove dependency on @textlint/kernel from formatter packages to maintain clean architecture
- Update all 10 formatters: stylish, compact, unix, table, checkstyle, junit, tap, pretty-error, fixer-formatter
- All tests continue to pass with numeric severity level checks

* docs: update formatter.md to document severity levels

- Add detailed explanation of severity levels (1: warning, 2: error, 3: info)
- Update examples to include severity property
- Remove outdated reference to SeverityLevel.js file
- Add practical examples showing info level usage

* test: add comprehensive tests for filter-severity-process

- Add tests for filterWarningMessages function to ensure it filters out info messages (severity 3) and warning messages (severity 1)
- Add tests for through function to verify it passes all messages unchanged
- Add tests for createSeverityFilter to verify --quiet flag behavior
- Ensure info messages are properly filtered when using --quiet mode
- Tests validate that only error messages (severity 2) are shown in quiet mode

* fix: correct table formatter test expectation for info severity

- Fix test case to expect '1 Info' instead of '1 Warning' for info severity (3)
- Update warningCount from 1 to 0 in test data to match actual behavior
- Info messages should be counted separately from warnings and errors
- Table formatter correctly displays info messages with their own category

* refactor: remove deprecated createFormatter test from linter formatter tests

* Add tests for various formatters in the linter-formatter package

- Implement tests for the pretty-error formatter to validate error output formatting.
- Add tests for the stylish formatter to ensure correct handling of messages and severity levels.
- Create tests for the table formatter to verify the output structure for different message scenarios.
- Introduce tests for the tap formatter to check the output format for single and multiple messages.
- Develop tests for the unix formatter to confirm the correct formatting of error messages across multiple files.

* refactor: update table formatter tests to use expect and inline snapshots

* refactor: remove deprecated tests and add new comprehensive tests for formatter functionality

* refactor: streamline error summary formatting in stylish formatter and tests

* refactor: remove unused dependencies from package.json and pnpm-lock.yaml

Co-authored-by: azu <azu@users.noreply.github.com>