* Upgrade npm in build-ubuntu
* npm i -S moment
* Don't upgrade npm
* macos-latest on build-mac
* Update dev-release.yml
* Add CI for macOS
* Lower password hash during unit tests
* Add comment
* Only integration tests on Windows
* Tweak TestCreateRecurringTask timings
* Fix server-test-mini-sqlite
* Upgrade npm in build-ubuntu
* npm i -S moment
* Don't upgrade npm
* macos-latest on build-mac
* Update dev-release.yml
* Support Windows in import archive and tests
* Run CI on Windows too
* CI: Windows SQLite only
* Remove npm ci fromn Windows CI
* Trying to parallize tests
* Fixing yml syntax
* Split server and webapp tets
* Trying to fix the ci server build
* Trying to fix the ci server build
* Trying to fix the ci.yml file
* Upgrade npm in build-ubuntu
* npm i -S moment
* Don't upgrade npm
* macos-latest on build-mac
* Update dev-release.yml
* Use windows-2022
* Debug: Dir
* Win SDK path
* Dir
* Use Win SDK 10.0.19041.0
* Cleanup
* Add Win requirements to readme
* Add Windows SDK download link to readme
Github Action for Scorecard
https://github.com/ossf/scorecard
The Scorecard provides a (somewhat opinionated) view on the security posture of the repository -- we (the product security team) would like to adopt this on our key repositories to identify possible security improvements
* Update focalboard to be compatible with mattermost v6
* Point to the new plugin API version
* Fix collectors linter issues
* Move all CI jobs to 1.16
* File `package-lock.json` updated.
* Use `cross-env` for setting environment variables in npm scripts.
* Remove all the mentions of `win-node-env` because it is no longer needed for running npm scripts.
Co-authored-by: Chen-I Lim <46905241+chenilim@users.noreply.github.com>
* New template for requesting doc improvements
I wanted to request a doc improvement and there wasn't a template to do so
* Rename doc_improvement to doc_improvement.md
* Update doc_improvement.md
* Update doc_improvement.md
* Adds plugin actions to the project's CI
* Remove the version number from the generated artifact
* Change job name to something more descriptive
* Switch back to workflow_dispatch
* Fixed#269
* Fixing checkbox widht
* Fix#274. Add re-login button to error page.
* Fix#276. Login page title
* Rev Mac build version
* Update changelog for v0.6.5
* Rev Mac build number
* GitHub Actions: Build with Xcode 12.4
* Fix#297: Mac keybpard handling
* Rev Mac built to 12
Co-authored-by: Jesús Espino <jespinog@gmail.com>
We had this problem in Mattermost where when we used the term "Feature Requests" it sounded a bit like "Pull Requests" and there was an expectation sometimes, in our own team and in the community, that it was some sort of formal ticket that had to be addressed.
We later changed to "Feature Idea" and then the expectations changed, where the maintainers didn't necessarily need to address every new ticket, since it was more sharing an idea, versus putting in a request.
Right now the volume of feature ideas is a little overwhelming and my sense is we should make this change to lower the perceived pressure a bit.
If we make this change, we can go update the previous tickets to match, and link to this ticket to explain why.
