Skip to content

docs: update developer guide #1093

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

docs: update developer guide #1093

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 3 additions & 12 deletions docs/developer-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ $ npm run test browser

## Pull Requests

Any intended change to the code base must open a [pull request](https://help.github.com/articles/creating-a-pull-request/) and be approved.
Any intended change to the code base must open a [pull request](https://help.github.com/articles/creating-a-pull-request/) and be approved.

Generally speaking, all PRs are open against the `master` branch, unless the feature being affected no longer exists on master.

Expand Down Expand Up @@ -213,20 +213,11 @@ Only the `master` branch and the `<latest>-release` branch are actively maintain
```bash
$ cd website
$ yarn
$ yarn start
$ yarn develop
```

4. Build and publish the website:

```bash
$ yarn build
$ git checkout gh-pages
```

Copy the content from `website/dist` to the root of the project. Commit with the corresponding release version:

```bash
$ git add .
$ git commit -m "3.3.4"
$ git push
$ yarn deploy
```