docs: explain there is no need to restart the Next.js server when upd…

…ating schema

.github/workflows/CI.yml

@@ -49,7 +49,6 @@ jobs:
         run: npm run build
         env:
           SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
-          NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: ${{ secrets.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY }}
 
       - if: github.event_name == 'pull_request'
         name: Validate all commits from PR
@@ -79,7 +78,6 @@ jobs:
         run: npx percy exec -- npm run test:e2e
         env:
           PERCY_TOKEN: ${{ secrets.PERCY_TOKEN }}
-          NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: ${{ secrets.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY }}
           CLERK_SECRET_KEY: ${{ secrets.CLERK_SECRET_KEY }}
 
       - uses: actions/upload-artifact@v3

README.md

@@ -256,7 +256,7 @@ After making changes to the schema, generate a migration by running the followin
 npm run db:generate
 ```
 
-This will create a migration file that reflects your schema changes. The migration is automatically applied during the next database interaction, so there is no need to run it manually.
+This will create a migration file that reflects your schema changes. The migration is automatically applied during the next database interaction, so there is no need to run it manually or restart the Next.js server.
 
 ### Commit Message Format
 

src/models/Schema.ts

@@ -8,7 +8,7 @@ import { integer, pgTable, serial, timestamp } from 'drizzle-orm/pg-core';
 
 // The generated migration file will reflect your schema changes.
 // The migration is automatically applied during the next database interaction,
-// so there's no need to run it manually.
+// so there's no need to run it manually or restart the Next.js server.
 
 export const counterSchema = pgTable('counter', {
   id: serial('id').primaryKey(),