Fix typos#2077
Conversation
|
Smoke (latest, CodingStyle) started failing 2 days ago. -> #2078 |
|
May I contribute a new CI workflow that regenerates (and commits) generated files? |
In past we have been using that, but it turned out more commits are harded to work with, so we have CI to assert all files are up-to-date, but you have to commit them manually from your side - you changed JS files, you need to rebuild them and commit. |
Could you please do that for me this time? |
|
In |
|
Done. |
|
It would be much better (no stomach pain for viktor) to set {
"engines": {
"node": "^18.12",
"npm": "^9.2.0",
"yarn": "please-use-npm"
}
}And npm install should be npm ci to leave the lock file unchanged. |
we use
|
Here "ci" does not mean "continuous integration" but clean install. |
I was running only |
|
How viable is to add https://github.com/crate-ci/typos into our CI for atk4/{core, data, ui}? Can we run it without any false positives out of the box? |
Here is how to do that. yarn import # import npm's package-lock.json
yarn install --frozen-lockfile |
That is a default workflow in my work. I was planning to improve your CI workflows. |
From atk4/data#1104
@mvorisek