Automation for building / testing the site
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 25
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Described at README there's a mention to generation via GHPages. In other projects we can see either their own CI/CD doing the builds or allowing 'travis-ci.org' 'free tier' to build and test and other services like netlify to 'render' the PR 'live'
For example: PR: https://github.com/Pelican-Elegant/elegant/pull/448
'Rendered' preview: https://deploy-preview-448--pelicanelegant.netlify.com/
Travis build: https://travis-ci.org/Pelican-Elegant/elegant/builds/559242879?utm_source=github_status&utm_medium=notification
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
Start by reading the README section describing generation via GHPages and inspect the repository's current site-build path. Compare the Travis CI and Netlify examples linked in the issue, then define an automation setup that builds and tests the site and provides a live pull-request preview. Done means the documented workflow runs successfully for changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, scss
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100