Skip to content

Latest commit

 

History

History
56 lines (35 loc) · 2.45 KB

README.md

File metadata and controls

56 lines (35 loc) · 2.45 KB

This is a Next.js project bootstrapped with create-next-app.

Translations on Hosted Weblate

Translation status

Getting Started

First, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

Start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello.
This endpoint can be edited in pages/api/hello.js.

The pages/api directory is mapped to /api/*.
Files in this directory are treated as API routes instead of React pages.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository — your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

Development Flow

Hey the formatting and lint rules are messing with my Git history

Yeah, as we evolve our coding standards and practices that will happen as we keep everything as up to date as possible, sorry :(
Luckily, there is a fix! We have a .git-blame-ignore-revs file that calls out specific problematic commits that were the result of ONLY doing lint fixes and you're local machine can be configured to use that file as a list of commits that should be ignored while doing blames and showing inline file history.
This can be configured by running

git config --global blame.ignoreRevsFile .git-blame-ignore-revs

Which was taken from https://michaelheap.com/git-ignore-rev/