Closed GrylledCheez closed 1 year ago
Is it necessary to commit the node_modules folder? Could you add it to .gitignore?
I guess you're right
Hey @GrylledCheez, please roll back the commits or start a new branch pre-merge without node_modules
. Having the commit included increases the size of the repo significantly.
This may need to be started in a fully separate branch as a patch to get rid of the history completely. Thanks!
@Fmstrat, did that work?
All js files linted
I didn't increment the version, since it's not functionally different to the v10 release. Feel free to inc it if you want.
What's the concensus for adding hooks/pre-commit that will run eslint before accepting a commit? https://gist.github.com/broofa/730fab6ceb1686f4a1fa9977b791b1b5
@phavekes, stop force pushing. Just do single commits. We can squash them in a rebase later.
@phavekes, stop force pushing. Just do single commits. We can squash them in a rebase later.
Sorry for that. Can't get eslint to work in GHA.
For some reason, your commit messed up the tabbing in the .eslintrc.yml for
- 'CallExpression[callee.object.name=GObject][callee.property.name=registerClass] > ClassExpression:first-child'
It should line up with the comments above it
@phavekes, I'm going to revert and force push back, and we can pretend none of this happened :D This branch is cursed.
be sure to do a git fetch --all
to make sure you have a clean history
I'm going to abandon this branch for now. But we will still need to do lining before the next version. For now keep pulling to the develop branch and we can do a lint there when we're ready.
only a few errors left. but I'm tired