rampatra/wedding-website

Move to the new GitHub Workflow to deploy the website to github pages

Open

#78 opened on Mar 2, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (1,453 stars) (778 forks)batch import
enhancementhelp wanted

Description

Currently, this uses the traditional deploy to github pages method (you can see it in Settings > Github Pages). However, Github has introduced a new Workflow feature (still in Beta) that allows us to have more control of the deployment process. This task is to move to this new Workflow approach.

I have taken a stab at it here - https://github.com/rampatra/wedding-website/blob/master/.github/workflows/npm-gulp.yml, however, there are some issues that need to be resolved and should be done as part of this ticket. Once done, we can get rid of the fallback approach in index.html for node_modules.

Contributor guide

Tech stack
javascriptnodejsgithub actions
Domain
ci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub ActionsnpmYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
First, examine the referenced workflow file at `.github/workflows/npm gulp.yml` to understand the existing issues. Also, look at `index.html` to identify the fallback approach for node modules that should be removed once the workflow is fixed. Then, review GitHub's documentation on the new GitHub Actions deployment workflow to pages.