Skip to content

Conversation

@jaidev17
Copy link
Contributor

  • Create new workflow - Spelling and Hyperlinks Check; and removed the old Check Code Quality workflow.
  • Create new spell-and-link-check.yml workflow with inline results display.
  • Disable content-checks.yml legacy workflow (preserved for reference)
  • Update .wordlist.txt: added valid technical terms

…list

- Create new spell-and-link-check.yml workflow with inline results display
- Add ANSI color code stripping for clean HTML link check output
- Disable content-checks.yml legacy workflow (preserved for reference)
- Update .wordlist.txt: add 26 valid technical terms, remove 18 typos
@jasonrandrews jasonrandrews merged commit 43c4aeb into ArmDeveloperEcosystem:main Jan 20, 2026
1 check passed
@annietllnd annietllnd self-requested a review January 20, 2026 19:18
Copy link
Collaborator

@annietllnd annietllnd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look great, thank you! If you could go through the remaining spell check issues and address them in the content, or add it to the list: https://github.com/ArmDeveloperEcosystem/arm-learning-paths/actions/runs/21184353851

For example, avilable is a spelling error, but something like pthread would be a word to add. Feel free to make your own assessment and let me know if you need some guidance on some of them :) You can open a new PR for this.

Thank you so much!

@jasonrandrews
Copy link
Contributor

@annietllnd Likely the misspelled words are in draft articles. I usually don't fix them while in draft because it will cause a conflict if the review is in process, and they will almost always be fixed during editorial. A new feature idea would be to filter out the spelling errors for articles that are in draft mode so we just ignore them. Basically, only spell check the non-draft articles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants