Skip to content

Comments

Create nextjs.yml#28

Merged
Dargon789 merged 1 commit intomasterfrom
Dargon789-patch-1
Apr 27, 2025
Merged

Create nextjs.yml#28
Dargon789 merged 1 commit intomasterfrom
Dargon789-patch-1

Conversation

@Dargon789
Copy link
Owner

@Dargon789 Dargon789 commented Apr 27, 2025

Summary by Sourcery

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

CI:

  • Introduce a workflow triggered on push to the master branch and manual dispatch.
  • The workflow builds the Next.js application using Node.js 20, automatically detecting the package manager.
  • Cache dependencies and Next.js build output to speed up subsequent runs.
  • Deploy the built static site artifact to GitHub Pages.

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@codesandbox
Copy link

codesandbox bot commented Apr 27, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link

sourcery-ai bot commented Apr 27, 2025

Reviewer's Guide by Sourcery

This pull request introduces a new GitHub Actions workflow file (.github/workflows/nextjs.yml) to automate the build and deployment of a Next.js application to GitHub Pages. The workflow is triggered on pushes to the master branch or via manual dispatch.

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

File-Level Changes

Change Details Files
Define the GitHub Actions workflow and its basic configuration.
  • Set the workflow name 'Deploy Next.js site to Pages'.
  • Configure triggers for push to 'master' branch and manual workflow dispatch.
  • Set necessary permissions (read contents, write pages, write id-token) for GitHub Pages deployment.
  • Configure concurrency settings to manage workflow runs.
.github/workflows/nextjs.yml
Implement the build job for the Next.js application.
  • Checkout the repository code.
  • Add a step to detect the package manager (yarn or npm).
  • Set up Node.js environment (version 20) with package manager caching.
  • Configure GitHub Pages integration specifically for Next.js static site generation.
  • Implement caching for the Next.js build output.
  • Install project dependencies using the detected package manager.
  • Build the Next.js project.
  • Upload the build output directory ('./out') as a workflow artifact.
.github/workflows/nextjs.yml
Implement the deployment job to GitHub Pages.
  • Define the deployment environment as 'github-pages'.
  • Set the deployment job to depend on the successful completion of the build job.
  • Use the actions/deploy-pages@v4 action to deploy the previously uploaded artifact to GitHub Pages.
.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

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Overall Comments:

  • Please ensure the workflow trigger uses the correct default branch (master is specified).
  • Ensure the Next.js project is configured for static export, as this workflow uploads the ./out directory.
Here's what I looked at during the review
  • 🟡 General issues: 1 issue found
  • 🟢 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 ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@Dargon789 Dargon789 merged commit aa350b4 into master Apr 27, 2025
13 of 15 checks passed
@Dargon789 Dargon789 deleted the Dargon789-patch-1 branch April 27, 2025 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant