* Adjust `package.json`s to pnpm
* Convert resolutions (pnpm doesn't support `**/` syntax)
It also removes resolutions that are no longer relevant.
* Convert `yarn.lock` to `pnpm-lock.yaml` with `pnpm import`
* Always add `e/web/teleport` workspace to the lockfile
* Adjust `jest` to new node_modules structure
* Adjust `storybook` to new node_modules structure
* Replace `toHaveStyleRule` with `toHaveStyle`
`jest-styled-components` package is no longer global, so `toHaveStyleRule` matchers is not recognized by TS.
We use them only in three places, so it's simpler to convert them to `toHaveStyle`.
* Adjust README files
* Adjust GHA workflows
* Adjust build assets
* Remove remaining `yarn` mentions
I don't think anyone uses the debug configuration for electron (and we don't have `start-electron` script for a long time).
* `corepack enable` -> `corepack enable pnpm`
* Automatically enable pnpm when running `make build/teleport`
* Run `pnpm import` again
* Run `pnpm dedupe`
* Add `yarn.lock` to .gitignore
* Link to pnpm installation docs
* Add a better comment for `transformIgnorePatterns`
* Make pattern for `shared` stories more specific
* Change `corepack enable pnpm` in readmes
* Run `pnpm import && pnpm dedupe` again
- Allow empty commits (in the event nothing changed)
- Include git status to help with troubleshooting
- Attempt to fix the webassets push with a fresh checkout
Rather than checking out master and then switching to the appropriate
branch, we just check out the right branch from the beginning.
This works because the branches in gravitational/webassets match up
with the branches in this repository.
This will run using a service account which is the only account
permitted to push to webassets and webassets.e.
The action will run when any commits are pushed to the protected
branches in webapps. This means that commits to webapps.e do not
directly trigger updates - this automation will run when the
enterprise submodule ref is updated in webapps.
The "nop" yarn script allows us to separate the building of the docker
image from the build of Teleport, so that GitHub actions can run the
yarn build after buildling an image from our dockerfile. This is
necessary because container steps do not support build args.
Grzegorz Zdunek