Skip to content
Snippets Groups Projects
Commit 9618cf41 authored by Richard Soderberg's avatar Richard Soderberg
Browse files

switch inline hyperlinks to markdown links

parent 48f28b9b
No related branches found
No related tags found
No related merge requests found
......@@ -57,7 +57,7 @@ You can control which tests are run using the `WHAT_TESTS` env var, see
Integration tests are done with [Travis-CI]. It is recommended that you setup [Travis-CI] for your BrowserID fork so that tests are automatically run when you push changes. This will give the BrowserID team confidence that your changes both function correctly and do not cause regressions in other parts of the code. Configuration files are already included in the repo but some setup is necessary.
1. Sign in to [GitHub]
2. Open http://travis-ci.org
2. Open [Travis-CI]
3. Click "Sign in with GitHub" if you are not signed in. If you are signed in, click on your username then "Profile" and go to step 5.
4. Click "Allow" if this is your first time signing in.
5. Find "browserid" in "Your Repositories"
......@@ -66,7 +66,7 @@ Integration tests are done with [Travis-CI]. It is recommended that you setup [T
8. Click the "Admin" button
9. Click "Service Hooks"
10. Ensure that "Travis" has a green radio button
11. Push to your fork and return to http://travis-ci.org Watch the tests run.
11. Push to your fork and return to [Travis-CI]. Watch the tests run.
[Travis-CI]: http://travis-ci.org
[GitHub]: https://github.com
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment