Skip to content
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.

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

Fixes #1314 - CONTRIBUTING Guidelines cleanup #1351

Merged
merged 7 commits into from
Mar 3, 2017
Merged

Conversation

zoepage
Copy link
Member

@zoepage zoepage commented Feb 20, 2017

See #1314

Overall list:

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

zoepage commented Mar 1, 2017

r? @miketaylr

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

Sad, our tests are being flaky again. :(

(unrelated to these changes)

@zoepage
Copy link
Member Author

zoepage commented Mar 1, 2017

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

Copy link
Member

@miketaylr miketaylr left a comment

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.

CONTRIBUTING.md Outdated
@@ -337,19 +369,23 @@ You can now edit `secrets.py` and

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.

CONTRIBUTING.md Outdated
@@ -375,7 +411,7 @@ You should now have a local instance of the site running at `http://localhost:50

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
Copy link
Member Author

zoepage commented Mar 3, 2017

@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