3b7049c5b7
I've done this process enough times that I should have written a script to do it a while ago. This one is rough, but the whole changelog process is pretty rough. This script takes multiple revision ranges and produces something that looks like a rough untranslated changelog, with indicators for how many of the provided ranges had the same change (deduplicated by title.) I use a process like this to build the Stable and Preview release notes out of a set of revision ranges. |
||
|---|---|---|
| .. | ||
| allow.txt | ||
| apis.txt | ||
| chinese.txt | ||
| colors.txt | ||
| fonts.txt | ||
| japanese.txt | ||
| math.txt | ||
| microsoft.txt | ||
| names.txt | ||
| README.md | ||
Allow files are lists of words to accept unconditionally
While check spelling will complain about an expected word which is no longer present, you can include things here even if they are not otherwise present in the repository.
E.g., you could include a list of system APIs here, or potential contributors (so that if a future commit includes their name, it'll be accepted).
Files
| File | Description |
|---|---|
| Allow | Supplements to the dictionary |
| Chinese | Chinese words |
| Japanese | Japanese words |
| Microsoft | Microsoft brand items |
| Fonts | Font names |
| Names | Names of people |
| Colors | Names of color |