actions/typos
1
0
Fork 0
mirror of https://github.com/crate-ci/typos.git synced 2024-11-22 00:51:11 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
1340 commits 2 branches 492 tags 34 MiB
Commit graph

1340 commits

This branch
This branch
All branches
Author SHA1 Message Date
Ed Page
64e40cffee chore: Release 2023-04-19 09:47:11 -05:00
Ed Page
6179ea546b docs: Update changelog 2023-04-19 09:47:00 -05:00
Ed Page
54042f2124 chore(ci): Build musl wheels 2023-04-19 09:46:47 -05:00
Ed Page
78058ce3e3 chore: Release 2023-04-19 08:35:04 -05:00
Ed Page
ea878c5094 docs: Update changelog 2023-04-19 08:34:35 -05:00
Ed Page
2a33141b90 fix(pre): Try to get typos-src to work 2023-04-19 08:34:07 -05:00
Ed Page
7f65ff4f24 chore: Release 2023-04-12 22:24:06 -05:00
Ed Page
0c7f963689 docs: Update changelog 2023-04-12 22:23:41 -05:00
Ed Page
3d31a296c4
Merge pull request #712 from epage/update 
chore: Update anstyle
 2023-04-13 11:32:56 -05:00
Ed Page
5145767575 chore: Update anstyle 2023-04-12 21:52:15 -05:00
Ed Page
217e403326 docs(cli): Show SSL cipher suites 
See #438
 2023-04-11 01:17:33 -05:00
Ed Page
66d82e5e51 chore: Release 2023-03-30 07:50:08 -05:00
Ed Page
8db59330b7 test(cli): Add UTF16 test 2023-03-30 07:45:24 -05:00
Ed Page
1c4dbcd5dd docs: Update changelog 2023-03-30 07:44:55 -05:00
Ed Page
37d90c230e
Merge pull request #706 from epage/utf16 
fix(cli): Actually decode UTF-16
 2023-04-04 09:20:13 -05:00
Ed Page
ae7f313230 fix(cli): Actually decode UTF-16 
Two problems
- I thought we had a UTF-16 test but apparently we didn't
- I didn't read enough fine print in the `encoding_rs` API

These combined meant the last release completely broke UTF-16 support.
 2023-03-30 07:27:55 -05:00
Ed Page
144ee4d018 chore: Release 2023-03-29 21:55:35 -05:00
Ed Page
15cdad2a3f chore: Release 2023-03-29 21:54:57 -05:00
Ed Page
db1950c95f docs: Update changelog 2023-03-29 21:54:24 -05:00
Ed Page
bbda5ff582
Merge pull request #704 from epage/dict 
fix(dict): Add March's typos
 2023-04-03 10:31:35 -05:00
Ed Page
e10e0d20da
Merge pull request #703 from epage/enc 
refactor: Switch out the UTF-16 encoding impl
 2023-04-03 09:50:22 -05:00
renovate[bot]
e1a138b637 chore(deps): update compatible 2023-04-01 07:05:05 +00:00
Ed Page
039edba3de fix(dict): Add March's typos 
Fixes #677
 2023-03-29 21:40:36 -05:00
Ed Page
98be58dbc9 refactor: Switch out the UTF-16 encoding impl 
Fixes #702
 2023-03-29 20:42:48 -05:00
Ed Page
6cf303d421 chore: Release 2023-03-18 04:20:06 -05:00
Ed Page
433b736d58 docs: Update changelog 2023-03-18 04:19:58 -05:00
Ed Page
53e2855fa0 chore: Release 2023-03-18 04:19:19 -05:00
Ed Page
8a6fc1895d chore: Release 2023-03-18 04:18:47 -05:00
Ed Page
c504325218
Merge pull request #697 from epage/update 
chore: Update winnow
 2023-03-22 19:55:00 -05:00
Ed Page
243b4efc9e chore: Update winnow 2023-03-18 04:11:55 -05:00
Ed Page
08f154e45b test: Try to fix CI 2023-03-18 02:15:16 -05:00
Ed Page
e15de8b72e chore: Release 2023-03-18 02:09:49 -05:00
Ed Page
a8eb9b075b docs: Update changelog 2023-03-18 02:09:34 -05:00
Ed Page
5253e5589b
Merge pull request #695 from epage/ignore 
feat(config): Custom ignores
 2023-03-22 15:53:24 -05:00
Ed Page
0d46368bfa docs: Link to user-editable list of users 2023-03-18 02:08:10 -05:00
Ed Page
78062a8de7 chore(gh): Enable wiki 2023-03-18 01:49:06 -05:00
Ed Page
ac46a6ba54 feat(config): Custom ignores 
Typos primarily works off of identifiers and words.  We have built-in
support to detect constructs that span identifiers that should not be
spell checked, like UUIDs, emails, domains, etc.  This opens it up for
for user-defined identifier-spanning constructs using regexes via
`extend-ignore-re`.

This works differently than any of the previous ways of ignoring thing
because the regexes require extra parse passes.  Under the assumption
that (1) actual typos are rare and (2) number of files relying on
`extend-ignore-re` are rare, we only do these extra parse passes when a
typo is found, causing almost no performance hit in the expected case.

While this could be used for more generic types of ignores, it isn't the
most maintainable because it is separate from the source files in
question.  Ideally, we'd implement document settings / directives for
these cases (#316).
 2023-03-18 01:25:39 -05:00
Ed Page
9d376417a0 test: Baseline for generic ignore 2023-03-18 01:20:01 -05:00
Ed Page
a1a601195e chore: Release 2023-03-17 23:59:36 -05:00
Ed Page
2cf45c3eb0 docs: Update changelog 2023-03-17 23:59:20 -05:00
Ed Page
1aefbee825
Merge pull request #694 from epage/fix 
fix: Actuall ignore ignored identifiers
 2023-03-22 13:43:34 -05:00
Ed Page
e4d2d0e54d fix: Actuall ignore ignored identifiers 2023-03-17 23:47:25 -05:00
Ed Page
2ee6ef4654 test(cli): Show extend-ignore-identifiers-re bug 2023-03-17 23:45:54 -05:00
Ed Page
fc7dfba01b docs(reference): Fix glob field name 2023-03-17 23:37:57 -05:00
Ed Page
0eae00fee2 test(cli): Consolidate files 2023-03-17 23:30:24 -05:00
Ed Page
797574c10a chore: Release 2023-03-17 23:09:02 -05:00
Ed Page
67f34020bd docs: Update changelog 2023-03-17 23:08:45 -05:00
Ed Page
7e0c4c4456
Merge pull request #693 from epage/re 
feat(dict): extend-ignore-identifiers-re support
 2023-03-22 11:41:19 -05:00
Ed Page
af90817e50 feat(dict): extend-ignore-identifiers-re support 
This opens the door for users to provide patterns for identifiers that
are always valid.  The key limitation is "identifiers".  Run `typos
--identifiers` to verify what you are trying to write the regex for.

Fixes #651
 2023-03-17 22:40:55 -05:00
Ed Page
03286f0f82 chore: Release 2023-03-16 05:22:42 -05:00