Skip to content

[CI] Husky set up for pre-push hooks #353

Description

@novusnota

Should run necessary linting operations as close to how they are run in CI as possible, and vice versa.

Suggestions from verytactical:

  • Use proper TS instead of Bash scripts to list changed files (example)
  • Combine scripts into one .ts script to conserve github runners. Same script must be used on CI and for husky. Split into several PRs, migrating CI jobs one by one. Include
    • Formatting
    • Spelling (cspell-lib)
    • Redirects
    • Navigation
  • Ensure there is a centralized API for reporting issues and their fixes to Github.
  • Change CI job to use this script. Do Node.js install as the first action to ensure it's cached and works faster.
  • Call the script from a prepush husky hook. Do not add any precommit hooks, as they interfere with git rebase.

Activity

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

Metadata

Metadata

Assignees

Labels

prio: highASAP, deadline due yesterdayscope: ci/cdGitHub Actions (.github), related scripts, commit/push hooks (.husky)

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions