GitHub workflows are out of date
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 369
- PR merge metrics
- No merged PRs in 30d
Description
We need to align this repo with the module template (or some other project that not only publishes to NPM but also deploys a site).
Also see #144.
## Acceptance Criteria
- The set of GitHub workflows in this repo matches the set defined in the module template.
- We are using the same versions of actions as is used in the module template (`create-release-pr`, `npm-publish`, etc.)
- Merging a release PR automatically deploys to `https://metamask.github.io/test-dapp/` and also `https://metamask.github.io/test-dapp/`. (The former automatically redirects to the latter.)
- Pushing a commit to a release PR automatically deploys to `https://metamask.github.io/test-dapp/rc-`.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the current GitHub workflow files with the module template and review issue #144, starting with the workflow definitions and action versions named in the acceptance criteria. Verify the release and release-candidate deployment behavior and URLs; done when the workflow set, action versions, and all listed deployments match the criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100