errose28 opened a new pull request, #76:
URL: https://github.com/apache/ozone-site/pull/76

   ## Summary
   
   - Spelling:
     - Add [cpsell](https://cspell.org/) to CI to catch spelling errors.
     - Configure language specific dictionaries and add Ozone specific words
     - Add documentation in the contributing guide and job summary about 
updating the allowed word list, since this may need to evolve as docs are 
written.
     - Fix spelling errors in existing documentation so the job passes.
   
   - Static workflow
     - Add a new static workflow that must pass before the website 
build/run/publish workflows.
     - Use https://github.com/actions/setup-node to install pnpm dev 
dependencies in the runner for executing static checks.
     - Use pnpm dependency cache built in to the setup-node action.
   
   ## Jira
   
   HDDS-9868
   
   ## Testing
   
   - The new workflow should pass on this PR and no job summary will be output.
   - [On my 
fork](https://github.com/errose28/ozone-site/actions/runs/7981058519), spell 
check fails when errors are present and outputs a job summary that may be 
helpful to new contributors.
   - [On my 
fork](https://github.com/errose28/ozone-site/actions/runs/7979899143/job/21788372877)
 prior to spelling fixes, spelling errors in documents and file names were 
flagged.
   - An [initial passing 
run](https://github.com/errose28/ozone-site/actions/runs/7981077621/job/21792062753)
 created a pnpm [cache 
entry](https://github.com/errose28/ozone-site/actions/caches) for the pnpm 
dependencies. A [second 
run](https://github.com/errose28/ozone-site/actions/runs/7981225756/job/21792506088)
 re-used this cache entry.
     - Ultimately the dev dependency list is so small right now that this 
doesn't save much time. However since the setup-node action handles it for us 
we might as well use it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to