* Install knapsack pro
* Use knapsack pro command
* Lint
* Use chrome
* Add test file pattern
* Use two different tokens for knapsack
* Use the correct secret
* Update lockfile
* Fix conflict
* Remove redundant options
* Add explaining comment
* Remove outdated variables and steps
* Update comment
* Fix conflict
* Use the chrome we setup earlier
* Add back percy config
* Set knapsack pro branch
* Use github_env to get browser path
* Add badge to readme
* Update .github/workflows/cypress.yaml
Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>
* Apply prettier
---------
Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>
* Disable Percy
While visual regression testing is without doubt an essential part of
quality assurance, the way we're currently using Percy brings little
to no value while causing mainenance overhead. Therefore, we're disabling it
until we have figure out https://github.com/vector-im/wat-internal/issues/36
and https://github.com/vector-im/wat-internal/issues/56.
* Also disable nightly build
* Comment out Percy step instead of fiddling with the output value
* Appease the frigging linter
* Make README markdown more consistent
* Most lines were 80 characters wide, others not - make them all 80.
* Switch to === titles in README where possible
* Fix documentation to make `yarn test` work out of the box
Before, invoking `yarn test` croaked on a missing src/component-index.js
file. In another part of the README, the missing instruction to generate
this file was found.
* Fix CI: Unauthenticated git protocol on port 9418 is no longer supported
GitHub is deprecating the service which answered unauthenticated git
protocol requests. Either it happened already, or they are running
brownouts.
* This is where I meant to leave that comment
Co-authored-by: Andreas Motl <andreas.motl@panodata.org>
At the current time, we do not intend to do additional work specifically to
support Edge. If it works for most use cases, that's great, but we do not
intend to fix issues that affect only Edge.
Fixes https://github.com/vector-im/riot-web/issues/9201
Take advantage of Yarn's preservation of links while installing and set up links
first and install second. This should result in a small speedup since we no
longer install the published SDKs just to replace them on the next line.
Most `npm` operations are replaced with `yarn`, which generally has better
behavior. However, steps like publish that write to the NPM registry are left to
`npm`, which currently handles these tasks best.
Setting up the SDK for development, I noticed that 3 tests failed on
develop branch. Linking the JS SDK made the tests pass. It looks like
the assumption is that developers link against the develop branch
of JS SDK to develop the React SDK.
Clarify this in the readme for completeness sake.
Signed-off-by: Jason Robinson <jasonr@matrix.org>
It has been marked outdated for several years. Since it appears on the repo home
page, it makes the project feel unmaintained.
Signed-off-by: J. Ryan Stinnett <jryans@gmail.com>
As at the moment the Readme does not explain the structure of the code any more, the Readme has to be actualized.
(This is just a draft, to keep track of this Issue)
