-
### Describe what should be investigated or refactored
We should review and update our pre-commit hooks to better work with our current workflow/codeql.
### Links to any relevant code
https://git…
-
**Is your feature request related to a problem? Please describe.**
Follow code standards
-
## 📝 Summary
Lets improve the local checks done before pushing code to the Kibana repo.
## Why
Engineers are currently using Elastic's CI as the primary way to validate their code.
We have …
-
There are a few useful pre-commit hooks that should be run automatically on commit. They can be found in this example repository:
https://github.com/lorenzwalthert/precommit/blob/main/.pre-commit-h…
-
Open question about precommit hooks. We can create individual PR's if we agree.
- Unit Tests? Obviously need to improve testing as a whole but it can be good to ensure tests are ran.
- Linting wi…
-
Would be great if the formatter and tests were run before code was committed.
Vlek updated
9 months ago
-
https://stellarfoundation.slack.com/archives/C049E67BFSP/p1720544108927959
-
We've got a big backlog of fixes in trunk now -- time for a release you think @adiroiban ?
Maybe #604 should be resolved first, but nothing else is outstanding. (if we do the precommit hooks update…
-
They are driving me insane, I again got
```
✖ npx prettier --write:
[error] src/database/testing_data.ts: SyntaxError: Unexpected token, expected "}" (22:18)
[error] 1 | import * as Types …
-
**Is your feature request related to a problem? Please describe.**
It would be a better developer experience if lint checks were run as a Git precommit hook, as opposed to the somewhat longer feedbac…