n8n-io/n8n

mirror of https://github.com/n8n-io/n8n.git synced 2024-11-09 17:50:52 +03:00

fix(nodes-base): fix and harmonize all primaryDocumentation links (#4191 )

* fix(nodes-base): fix and harmonize all primaryDocumentation links

* feat(workflow, cli): expose documentation links to UI via node codex

* fix(editor-ui): link to correct node and credential documentation URLs

* config(nodes-base): update 'format' script to also format node descriptor json

* chore: fix outdated links to node reference documentation

2022-09-29 13:33:16 +03:00

6.2 KiB

Raw Blame History

Contributing to n8n

Great that you are here and you want to contribute to n8n

Code of Conduct
Directory Structure
Development Setup
Development Cycle
Create Custom Nodes
Create a new node to contribute to n8n
Checklist before submitting a new node
Extend Documentation
Contributor License Agreement

Code of conduct

This project and everyone participating in it are governed by the Code of Conduct which can be found in the file CODE_OF_CONDUCT.md. By participating, you are expected to uphold this code. Please report unacceptable behavior to jan@n8n.io.

Directory structure

n8n is split up in different modules which are all in a single mono repository.

The most important directories:

/docker/image - Dockerfiles to create n8n containers
/docker/compose - Examples Docker Setups
/packages - The different n8n modules
/packages/cli - CLI code to run front- & backend
/packages/core - Core code which handles workflow execution, active webhooks and workflows. Contact n8n before starting on any changes here
/packages/design-system - Vue frontend components
/packages/editor-ui - Vue frontend workflow editor
/packages/node-dev - CLI to create new n8n-nodes
/packages/nodes-base - Base n8n nodes
/packages/workflow - Workflow code with interfaces which get used by front- & backend

Development setup

If you want to change or extend n8n you have to make sure that all needed dependencies are installed and the packages get linked correctly. Here a short guide on how that can be done:

Requirements

Node.js

We suggest using Node.js version 16 for development purposes.

Build tools

The packages which n8n uses depend on a few build tools:

Debian/Ubuntu:

apt-get install -y build-essential python

CentOS:

yum install gcc gcc-c++ make

Windows:

npm install -g windows-build-tools

npm workspaces

n8n is split up in different modules which are all in a single mono repository. To facilitate the module management, npm workspaces are used. This automatically sets up file-links between modules which depend on each other.

Actual n8n setup

Important

: All the steps below have to get executed at least once to get the development setup up and running!

Now that everything n8n requires to run is installed the actual n8n code can be checked out and set up:

Fork the n8n repository

Clone your forked repository

git clone https://github.com/<your_github_username>/n8n.git

Go into repository folder
```
cd n8n
```
Add the original n8n repository as upstream to your forked repository
```
git remote add upstream https://github.com/n8n-io/n8n.git
```
Install all dependencies of all modules and link them together:
```
npm install
```
Build all the code:
```
npm run build
```

Start

To start n8n execute:

npm run start

To start n8n with tunnel:

./packages/cli/bin/n8n start --tunnel

Development cycle

While iterating on n8n modules code, you can run npm run dev. It will then automatically build your code, restart the backend and refresh the frontend (editor-ui) on every change you make.

Start n8n in development mode:
```
npm run dev
```
Hack, hack, hack
Check if everything still runs in production mode
```
npm run build
npm run start
```
Create tests
Run all tests
```
npm run test
```
Commit code and create a pull request

Test suite

The tests can be started via:

npm run test

If that gets executed in one of the package folders it will only run the tests of this package. If it gets executed in the n8n-root folder it will run all tests of all packages.

Create custom nodes

Important

: Avoid use of external libraries to ensure your custom nodes can be reviewed and merged quickly.

Learn about using the node dev CLI to create custom nodes for n8n.

More information can be found in the documentation of n8n-node-dev, a small CLI which helps with n8n-node-development.

Create a new node to contribute to n8n

Follow this tutorial on creating your first node for n8n.

Checklist before submitting a new node

There are several things to keep in mind when creating a node. To help you, we prepared a checklist that covers the requirements for creating nodes, from preparation to submission. This will help us be quicker to review and merge your PR.

Extend documentation

The repository for the n8n documentation on docs.n8n.io can be found here.

Contributor License Agreement

That we do not have any potential problems later it is sadly necessary to sign a Contributor License Agreement. That can be done literally with the push of a button.

We used the most simple one that exists. It is from Indie Open Source which uses plain English and is literally only a few lines long.

A bot will automatically comment on the pull request once it got opened asking for the agreement to be signed. Before it did not get signed it is sadly not possible to merge it in.

6.2 KiB Raw Blame History