Skip to content

Update workshop title to include 'For NextJS'#13

Open
SeanMcTernan wants to merge 2 commits into
mainfrom
staging
Open

Update workshop title to include 'For NextJS'#13
SeanMcTernan wants to merge 2 commits into
mainfrom
staging

Conversation

@SeanMcTernan
Copy link
Copy Markdown
Contributor

No description provided.

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 20, 2026

Deploy Preview for primitives-demo ready!

Name Link
🔨 Latest commit c2ae90d
🔍 Latest deploy log https://app.netlify.com/projects/primitives-demo/deploys/69eb811d98a8ac00081fc3f8
😎 Deploy Preview https://deploy-preview-13--primitives-demo.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 20, 2026

Deploy Preview for keen-pixie-e5359e failed. Why did it fail? →

Name Link
🔨 Latest commit c2ae90d
🔍 Latest deploy log https://app.netlify.com/projects/keen-pixie-e5359e/deploys/69eb811debd2e3000868a65b

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 20, 2026

Deploy Preview for netlify-core-workshop ready!

Name Link
🔨 Latest commit c2ae90d
🔍 Latest deploy log https://app.netlify.com/projects/netlify-core-workshop/deploys/69eb811debd2e3000868a657
😎 Deploy Preview https://deploy-preview-13--netlify-core-workshop.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dbfe2cca-d2fa-4c73-908a-f849f62d7f2a

📥 Commits

Reviewing files that changed from the base of the PR and between df5e590 and c2ae90d.

📒 Files selected for processing (1)
  • README.md
✅ Files skipped from review due to trivial changes (1)
  • README.md

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated README H1 to "Netlify Core Workshop For Next" to clarify the workshop is tailored for Next.js applications, improving title accuracy and discoverability.
    • No other workshop content or public APIs were modified.

Walkthrough

The README.md file's primary heading was changed from "Netlify Core Workshop" to "Netlify Core Workshop For Next". This is a single-line text update to the top-level H1 in the documentation; no other content or exported/public entities were modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No pull request description was provided by the author. While ideally a description would be present, this is a very lenient check and passes as long as it is not completely off-topic. Consider adding a brief description explaining why the workshop title is being updated to include 'For NextJS' and any related context.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The PR title accurately describes the main change: updating the workshop title to include 'For NextJS', which matches the README.md header change from 'Netlify Core Workshop' to 'Netlify Core Workshop For Next'.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch staging

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@SeanMcTernan
Copy link
Copy Markdown
Contributor Author

screenshot

This needs changing now!

Browser metadata
Path:      /
Browser:   Chrome 146.0.0.0 on Mac OS 10.15.7
Viewport:  1908 x 918 @1x
Language:  en-US
Cookies:   Enabled

Open in BrowserStack

Open Deploy Preview · Mark as Resolved

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
README.md (1)

1-1: Consider using the official "Next.js" branding.

The framework's official branding is "Next.js" (with a lowercase 'j', lowercase 's', and a period), not "NextJS". This aligns with how the project is officially named by Vercel.

📝 Suggested branding correction
-# Netlify Core Workshop For NextJS
+# Netlify Core Workshop For Next.js
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 1, Update the README header text that currently reads
"Netlify Core Workshop For NextJS" to use the official Next.js branding
("Next.js") so it becomes "Netlify Core Workshop For Next.js"; locate and change
the header/title string in the README (the line containing "Netlify Core
Workshop For NextJS") to reflect this exact capitalization and punctuation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Line 1: Update the README header text that currently reads "Netlify Core
Workshop For NextJS" to use the official Next.js branding ("Next.js") so it
becomes "Netlify Core Workshop For Next.js"; locate and change the header/title
string in the README (the line containing "Netlify Core Workshop For NextJS") to
reflect this exact capitalization and punctuation.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e62795a7-6e66-4b72-a92d-b8f9adbe5dac

📥 Commits

Reviewing files that changed from the base of the PR and between 8e59b8e and df5e590.

📒 Files selected for processing (1)
  • README.md

Updated workshop title to reflect NextJS focus.
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