Skip to content

Latest commit

 

History

History
150 lines (96 loc) · 3.13 KB

CONTRIBUTING.md

File metadata and controls

150 lines (96 loc) · 3.13 KB
Raw

CONTRIBUTING

Contributions are always welcome, no matter how large or small. Before contributing, please read the code of conduct.

For details on contributing to documentation, see Website Directory Readme.

Setup

Install Node.js (LTS) on your system: https://nodejs.org/

Install yarn on your system: https://yarnpkg.com/en/docs/install

Install dependencies

Only required on the first run, subsequent runs can use yarn start to both bootstrap and run the development server.

$ git clone https://github.com/netlify/netlify-cms
$ cd netlify-cms
$ yarn
$ yarn bootstrap

Run locally

yarn start

Available scripts

bootstrap

Bootstraps the monorepo.

yarn bootstrap

watch

Watches all CMS packages and transpiles them on change.

yarn watch

start

Starts the development server. This task runs both the bootstrap and watch scripts.

yarn start

clean

Removes all of the CMS package dist directories.

yarn clean

reset

Runs the clean script and removes all the node_modules from the CMS packages.

yarn reset

build

Runs the clean script and builds the CMS packages.

yarn build

build-preview

Runs the build and build-preview scripts in each package and serves the resulting build locally.

yarn build-preview

test

Runs linting and Jest tests.

yarn test

test:all

Runs linting, Jest, and Cypress tests.

yarn test:all

test:e2e

Runs Cypress e2e tests.

yarn test:e2e

test:e2e:dev

Runs Cypress e2e tests on watch mode with an open instance of Chrome.

yarn test:e2e:dev

format

Formats code and docs according to our style guidelines.

yarn format

Pull Requests

We actively welcome your pull requests!

If you need help with Git or our workflow, please ask in our community chat. We want your contributions even if you're just learning Git. Our maintainers are happy to help!

Netlify CMS uses the Forking Workflow + Feature Branches. Additionally, PR's should be rebased on master when opened, and again before merging.

  1. Fork the repo.
  2. Create a branch from master. If you're addressing a specific issue, prefix your branch name with the issue number.
  3. If you've added code that should be tested, add tests.
  4. If you've changed APIs, update the documentation.
  5. Run yarn test and ensure the test suite passes.
  6. Use yarn format to format and lint your code.
  7. PR's must be rebased before merge (feel free to ask for help).
  8. PR should be reviewed by two maintainers prior to merging.

License

By contributing to Netlify CMS, you agree that your contributions will be licensed under its MIT license.