Gamechanger JS/TS linting rules

Updating ES-Lint

Follow these steps to make updates to lint tools:

1. Make your updates locally. Be sure to run yarn to update lock files.
2. After your package version updates are made, be sure to update the package.json version. Ex: "version": "0.0.11" -> "version": "0.0.12"
3. Create tag
   • After merging your change, create a tag locally
   • switch to main branch and git pull origin main
   • create the tag: git tag vx.x.xx (replace with your version number)
   • push your tag: git push origin vx.x.xx (replace with your version number)
   • This will trigger the Publish workflow to push the new package.
4. In Eden, you can now update @gamechanger/eslint-plugin with the appropriate version number

---

Testing New Hooks or Rule Changes Without Publishing

1. Have Eden cloned side-by-side with this repo (e.g. my_dir/eden and my_dir/lint). Yes, you can do this from an Eden codespace by simply backing up one directory via cd .. and then cloning side-by-side in the /workspaces folder.
2. From a terminal in the Eden folder run this command

pre-commit try-repo ../lint eslint

---

Package Bumps

After updating dependencies, stage package.json and yarn.lock, then run pre-commit. This will update the .pre-commit-hooks.yaml additional_dependencies section. These must be kept in sync!

---