Create nextjs.yml

[Dargon789]

Summary by Sourcery

Add a GitHub Actions workflow to build and deploy the Next.js application to GitHub Pages.

CI:

• Configure a new workflow (nextjs.yml) triggered on pushes to the master branch and manually via workflow_dispatch.
• Implement a build job that checks out code, sets up Node.js, installs dependencies, builds the Next.js static site, and uploads the artifact.
• Implement a deployment job that uses the uploaded artifact to deploy the site to GitHub Pages.
• Set required permissions and concurrency settings for GitHub Pages deployment.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sourcery-ai]

Reviewer's Guide by Sourcery

Adds a GitHub Actions workflow for building and deploying a Next.js application to GitHub Pages.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Add GitHub Actions workflow file.	Create a new file for the Next.js CI/CD workflow.	.github/workflows/nextjs.yml
Configure workflow settings.	Specify workflow name and triggers. Grant necessary permissions for Pages deployment. Set up concurrency control.	.github/workflows/nextjs.yml
Define the build process.	Add steps for checking out code, detecting package manager, and setting up Node.js. Include configuration for GitHub Pages specific to Next.js. Implement caching for build artifacts. Add steps to install dependencies and build the project. Upload the generated site files as an artifact.	.github/workflows/nextjs.yml
Define the deployment process.	Create a deployment job dependent on the build. Configure the deployment environment. Use the GitHub Pages deploy action.	.github/workflows/nextjs.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[sourcery-ai]

Hey @Dargon789 - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider triggering this workflow on the main branch instead of master if that's the repository's default branch.
• Consider reading the Node.js version from a project file like .nvmrc or package.json instead of hardcoding '20'.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.55%. Comparing base (d7fc257) to head (15dd222).
Report is 2 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
block	84.33% <ø> (ø)
blockchain	89.32% <ø> (ø)
client	67.99% <ø> (ø)
common	97.51% <ø> (ø)
devp2p	86.78% <ø> (ø)
evm	73.11% <ø> (ø)
mpt	89.69% <ø> (-0.36%)	⬇️
statemanager	69.06% <ø> (ø)
static	99.11% <ø> (ø)
tx	90.59% <ø> (ø)
util	89.36% <ø> (ø)
vm	55.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.