- Allow CodeQL workflow to be run from GitHub Actions WebUI at any time
- Set CodeQL to also check for best practises/code problems (as well as security)
- Capitalize Publish GH Action
- Change Windows Test workflow for consistent file extension (also means its formatted with Prettier) and remove leading empty linebreak
- Run Prettier (maybe we should add this to build script to ensure all code is formatted?)
- Change .gitattributes to have LF line-endings for more file types
This change is done in order to ensure that Windows users don't
encounter any newline related issues.
e.g.: Prior to this change, after the build script was run, files
from `node_modules` (having `LF` newlines, and which wouldn't have
be normalized by `git`) would be copied to the `dist/` directory
and would appear to Windows users as if they where changed.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Thanks to @XhmikosR for pointing this out!
Ref http://git-scm.com/docs/gitattributes#_effectshttp://en.wikipedia.org/wiki/NewlineCloseh5bp/html5-boilerplate#1618
Under UNIX-like OSes, a text file consists of a series of lines, each
of which ends with a `newline` character (`\n`). A file that is not
empty and does not end with a `newline` is therefore considered not to
be a text file.
Because of this, utilities that are supposed to operate on text files
may not cope well with files that don't end with a `newline` (e.g.: they
might ignore the text after the last `newline`).
Adding the `newline` character at the end of the file ensures that users
won't encounter any odd behavior when using it.
Reference/Source: http://unix.stackexchange.com/a/18789.
