Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ yarn-error.log
.DS_Store

.env
.env.production
.firebase/*
coverage
.vscode
Expand Down
16 changes: 16 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,22 @@ In the case of an objection being raised in a pull request by another collaborat
* [`squash`][] pull-requests made up of multiple commits
* Land how you like as long as there are no merge commits

## Getting Started

For feature development you should be working from the staging branch.

* Fork
* Clone your fork `git clone git@github.com:<githubid>/nodejs.dev.git`
* cd into your project
* Add the following to your remotes by doing `git remote add upstream git@github.com:nodejs/nodejs.dev.git`
* Check out the staging branch by doing `git checkout upstream/staging`
* Create a new branch for your awesome work `git checkout -b branchname`
* Commit your work
* Push to your branch `git push -u origin yourbranch`
* Make a pull request against the remote branch `staging`
* Example `https://github.com/nodejs/nodejs.dev/pull/398`
* Mention @nodejs/website-redesign `/gcbrun`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think here we need to use /preview instead of /gcbrun?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh ya forgot about that change.


## Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:
Expand Down