This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

Some more small text changes (#235) #81

	# Sample workflow for building and deploying a Next.js site to GitHub Pages
	#
	# To get started with Next.js see: https://nextjs.org/docs/getting-started
	#
	name: Deploy Next.js site to Pages

	on:
	# Runs on pushes targeting the default branch
	push:
	branches: ["main"]

	# Allows you to run this workflow manually from the Actions tab
	workflow_dispatch:

	# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
	permissions:
	contents: read
	pages: write
	id-token: write

	# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
	# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
	concurrency:
	group: "pages"
	cancel-in-progress: false

	jobs:
	# Build job
	build:
	uses: ./.github/workflows/build.yml
	with:
	NEXT_PUBLIC_ONE_TRUST_DOMAIN_SCRIPT: 3a6bb61d-8924-4c57-a2b6-bd2306a9c5ef

	deploy:
	# Add a dependency to the build job
	needs: build

	# Grant GITHUB_TOKEN the permissions required to make a Pages deployment
	permissions:
	pages: write # to deploy to Pages
	id-token: write # to verify the deployment originates from an appropriate source

	# Deploy to the github-pages environment
	environment:
	name: github-pages
	url: ${{ steps.deployment.outputs.page_url }}

	# Specify runner + deployment step
	runs-on: ubuntu-latest
	steps:
	- name: Deploy to GitHub Pages
	id: deployment
	uses: actions/deploy-pages@v4

Provide feedback