Add eslint workflow action and CONTRIBUTING.md that says to lint first #66
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#73 Allow null and undefined values in persistent refs}
profectus/Profectus
Reference: profectus/Profectus#66
Loading…
Reference in a new issue
No description provided.
Delete branch "thepaperpilot/Profectus:feat/enforce-eslint"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #63
@ -0,0 +8,4 @@
## Contributing
Make sure to open your PR on Incremental Social - the GitHub repo is just a mirror!
I think this should have a link to the Incremental Social repo in this line, as not everyone will know what/where that is.
@ -0,0 +18,4 @@
Ensure that your changes pass all existing tests and, if applicable, add new tests to cover the changes you've made. Run `npm run test` to run all the tests.
## Code Style
Is this supposed to be a subcategory of Contributing (###) or a separate category (##)?
@ -0,0 +22,4 @@
We use ESLint and Prettier to enforce consistent code style throughout the project. Before submitting a PR, run `npm run lint:fix` to automatically fix any linting issues.
## Issue Reporting
Feel like Issue Reporting should go before Contributing, since it's likely more relevant to the average use case