Skip to content

Fixes #1314 - CONTRIBUTING Guidelines cleanup - #1351

Merged
miketaylr merged 7 commits into
masterfrom
issues/1314/1
Mar 3, 2017
Merged

Fixes #1314 - CONTRIBUTING Guidelines cleanup#1351
miketaylr merged 7 commits into
masterfrom
issues/1314/1

Conversation

@zoepage

@zoepage zoepage commented Feb 20, 2017

Copy link
Copy Markdown
Member

See #1314

Overall list:

@zoepage zoepage changed the title Fixes #1314 Fixes #1314 - CONTRIBUTING Guidelines cleanup Feb 20, 2017
@zoepage

zoepage commented Mar 1, 2017

Copy link
Copy Markdown
Member Author

r? @miketaylr

@miketaylr
miketaylr self-requested a review March 1, 2017 16:53
@miketaylr

Copy link
Copy Markdown
Member

Sad, our tests are being flaky again. :(

(unrelated to these changes)

@zoepage

zoepage commented Mar 1, 2017

Copy link
Copy Markdown
Member Author

Yes. It's again this one that fails :/

@miketaylr miketaylr left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good!

Just a few tiny fixes in comments.

Also, can you rebase against master? That should get rid of the merge commit.

Comment thread CONTRIBUTING.md Outdated
2. You have the option of creating a "bot account" (a dummy account for the purpose of testing), or using your own account for local development. Either way, you'll need a personal access token to proceed — this is the oauth token we use to report issues on behalf of people who don't want to give GitHub oauth access (or don't have GitHub accounts).

The [instructions for creating a personal access token](http://help.github.com/articles/creating-an-access-token-for-command-line-use) are given on GitHub. Select public_repo to grant access to the public repositories through the personal access token. Once you have created the token you can add it in the variable `OAUTH_TOKEN = ""` (yes, even if you're using your own credentials we still refer to it as a bot). More advanced users might want to create an environment variable called `OAUTH_TOKEN`. Either way is fine.
The [instructions for creating a personal access token](http://help.github.com/articles/creating-an-access-token-for-command-line-use) are given on GitHub. Select public_repo to grant access to the public repositories through the personal access token. Once you have created the token you can add it in the variable `OAUTH_TOKEN = ""` (yes, even if you're using your own credentials we still refer to it as a bot). More advanced users might want to create an environment variable called `OAUTH_TOKEN`. Either way is fine.

This comment was marked as abuse.

Comment thread CONTRIBUTING.md Outdated
After certain kinds of changes are made, you need to build the project before serving it from a webserver will work

* CSS: a build will run cssnext, combine custom media queries, and concat all source files into webcompat.dev.css. You'll need to re-build the CSS to see any changes, so it's recommended to use a watch task (see `make watch` or `grunt watch`).
* CSS: a build will run cssnext, combine custom media queries, and concat all source files into webcompat.dev.css. You'll need to re-build the CSS to see any changes, so it's recommended to use a watch task (see `make watch` or `npm run watch`).

This comment was marked as abuse.

@zoepage

zoepage commented Mar 3, 2017

Copy link
Copy Markdown
Member Author

@miketaylr done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants