* docs: update CONTRIBUTING.md
* docs: use db instead of database for more space
* docs: update CONTRIBUTING.md
* docs: update PR template
* docs: add note about skipping a release
* chore: use stale label, instead of wontfix
* chore: add link to issue explaining stalebot
* chore: fix typo in stalebot comment
* chore: run build GitHub Action on canary also
* chore: run build GitHub Actions on canary as well
* chore: add reproduction section to questions
Full end-to-end integration tests for Twitter (OAuth 1) and GitHub (OAuth 2) using Puppeteer and Mocha.
This replaces Cypress tests due to issues with Cypress not being able to run tests against external URLs, which we need for our integration tests.
The integration test runner is hosted outside of GitHub Actions (it cannot be hosted by GitHub or on AWS due to IP access controls placed on sign in by providers like Twitter and GitHub) and so the integration tests may not pass if the test runner is offline. If this happens, tests can be re-run later when the test runner is available.
See Pull Request #641 for details.
Have been the asked some questions a few times (including via email).
Most of the time these reports have already been addressed.
Trying to nudge behaviour to check the example project and docs first.
Also want to understand where people couldn't find what they needed.
Removed pre-filled issue title as people were forgetting to change it.
Trying to create some structure to get external contributors to think about feature requests and/or provide more information when raising issues.
This is not intended for core committers - I'm just trying to wrangle the input we get to reduce signal to noise, especially as I'm also starting to get emails asking for support now.
