* commit dummy workflow
* Update nextjs.yml
* renaming
* actually do a node build
* add jekyll build & deploy
* add permissions
* update jekyll to use composite upload action
* update next to use composite upload action
* update icon yml
* change nexjs icon
* Cleanup further the Jekyll template
* add gatsby starter workflow
* fix composite error
* fix updated actions
* Add Hugo
* Apply suggestions from code review
* Inital commit for nuxtjs starter workflow
* Cleanup all templates
* Add baseUrl through an action
* Use `base_url` output for Hugo configuration
* Create static.yml
* Create static.properties.json
* clarify path
* alternative jekyll icon with only tube
* use alternate jekyll icon
* use original xvg with proper viewBox parameters
* Add paper-spa/configure-pages to starter workflows
Replaces paper-spa/setup-pages where appropriate.
* use setup-ruby action instead of our container
* Add starter workflow for GitHub Pages's legacy Jekyll build
Named `jekyll-gh-pages` so that it connotes the familiar "hands off"
build process of the Jekyll build as performed by github pages workers,
without sounding deprecated by using the words "legacy" or "classic".
* Use the static_site_generator input so we can modify the correct config
* Update gatsby.yml
* Update wording on the 'legacy' jekyll workflow
* Fix filename: this should have a json extension
* Fix filename: this should have a .properties.json extension
* Update nextjs.properties.json
* Update static.properties.json
* Fix typo in name of Gatsby
* Remove pull_request triggers
* Update to latest versions of core Actions
* Remove '--if-present' flag from 'npm run build' commands to prevent silent failure
* Perform static HTML export for Next.js
* Add '--no-install' flag to 'npx' usage
* Update Nuxt starter workflow to run 'generate'
* Default to using npm if not using yarn
* Reword 'nuxt generate' step name
* Update pages/gatsby.yml
* Update description of Jekyll starter workflow
* Add configure-pages step to static workflow
* Add configuration step to enable Pages
* Pages: Set `PREFIX_PATHS` env var for Gatsby build
* Update Next.js starter workflow to cache builds
See https://nextjs.org/docs/advanced-features/ci-build-caching#github-actions
* Update NuxtJS starter workflow to cache builds
Basically modeled after the Gatsby starter workflow
* Call out node ssg getting started + setup
* Update nuxt documentation
* Retarget actions referencing `paper-spa` to `actions`
Also point to newly published `v1` tags rather than `main` or `v0`.
Co-authored-by: yimysty <yimysty@github.com>
Co-authored-by: Tommy Byrd <tcbyrd@github.com>
Co-authored-by: Yoann Chaudet <yoannchaudet@github.com>
Co-authored-by: Timothy <tjyung@github.com>
Co-authored-by: Smitha Borkar <12040799+smithaborkar@users.noreply.github.com>
Co-authored-by: James M. Greene <JamesMGreene@github.com>
* Upgrade Rails workflow to true CI
The existing Rails CI example only runs linters, which is not continuous
integration. This change brings the Rails example workflow up to par
with the other web framework CI flows, like Django.
This example is optimized for Rails 7, which does not include NodeJS,
webpack, or yarn by default. No Rails application code changes are
required for this flow to run the tests, and both minitest and rspec are
supported via the `test` rake task.
* add Rails icon
* use env vars, hopefully
* use the full hash for ruby/setup-ruby
* remove PORT since services cannot use it
* stop repeating identical step envs
* resolve env var declaration error
* update setup-ruby to the SHA of v1.92
* use setup-ruby SHA for lint job too
Co-authored-by: Bishal Prasad <bishal-pdmsft@github.com>
laurentsimon