terser / terser/terser.github.io
Prefer github actions over manual commits
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Instead of switching consistently from terser/website to terser/terser.github.io, wouldn't it be better to move terser/website to this repository, and add a github action that deploys the webpage from a github action?
The same can be said for terser/repl, which also lacks an auto-publishing github action.
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
Review how the terser/website and terser/repl repositories currently publish, then compare that with the terser/terser.github.io repository. Define the repository move and GitHub Actions deployment scope for both sites, including what successful automatic publishing should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100