Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-37819

[UI] change Husky to not letting commit pass if there are new i18n values

XMLWordPrintable

    • Tech debt kubevirt ui (updating)
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • To Do
    • qe-ready
    • Hide

      2024-03-11: Not  started yet...

      Show
      2024-03-11: Not  started yet...
    • ---
    • ---

      4.15:

      • change Husky to not letting commit pass if there are new i18n values

      Curently when sending a commit, husky runs before and run prettier, eslint and i18n , it will fail the commit if eslinter alerts/prettier. but if new keys are added to i18n , the commit will pass and then 1 files if left outside the commit, which is the new updated i18n json, a nice solution will be that if i18n json is updated and should be added to the commit, the commit will fail or the json file will be added automatically to the commit.

              tnisan@redhat.com Tal Nisan
              mschatzm@redhat.com Matan Schatzman
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: