Update the test/lint commands in the contribution templates

.github/CONTRIBUTING.md

@@ -37,7 +37,8 @@ reliably would also make a huge difference.
 * Use a topic branch to easily amend a pull request later, if necessary.
 * Use the same coding conventions as the rest of the project.
 * Verify your Emacs Lisp code with `checkdoc` (<kbd>C-c ? d</kbd>).
-* Make sure that the unit tests are passing (`make test`).
+* Make sure that the unit tests are passing (`eldev test`).
+* Make sure that there are no lint warnings (`eldev lint`).
 * Write [good commit messages][3].
 * Mention related tickets in the commit messages (e.g. `[Fix #N] Add command ...`).
 * Update the [changelog][6].

.github/PULL_REQUEST_TEMPLATE.md

@@ -8,8 +8,8 @@ by checking the relevant checkboxes):
 
 - [ ] The commits are consistent with our [contribution guidelines](../blob/master/.github/CONTRIBUTING.md)
 - [ ] You've added tests (if possible) to cover your change(s)
-- [ ] All tests are passing (`make test`)
-- [ ] All code passes the linter (`make lint`) which is based on [`elisp-lint`](https://github.com/gonewest818/elisp-lint) and includes
+- [ ] All tests are passing (`eldev test`)
+- [ ] All code passes the linter (`eldev lint`) which is based on [`elisp-lint`](https://github.com/gonewest818/elisp-lint) and includes
   - [byte-compilation](https://www.gnu.org/software/emacs/manual/html_node/elisp/Byte-Compilation.html), [`checkdoc`](https://www.gnu.org/software/emacs/manual/html_node/elisp/Tips.html), [check-declare](https://www.gnu.org/software/emacs/manual/html_node/elisp/Declaring-Functions.html), packaging metadata, indentation, and trailing whitespace checks.
 - [ ] You've updated the [changelog](../blob/master/CHANGELOG.md) (if adding/changing user-visible functionality)
 - [ ] You've updated the [user manual](../blob/master/doc) (if adding/changing user-visible functionality)