@@ -33,7 +33,7 @@ You can check if git support pcre by using the '-P' option
33
33
34
34
## Cloning repositories
35
35
36
- You should start forking the main ( metacpan-grep-front-end repository) [ https://github.com/metacpan/metacpan-grep-front-end ]
36
+ You should start forking the main [ metacpan-grep-front-end repository] ( https://github.com/metacpan/metacpan-grep-front-end )
37
37
You can then clone it locally (where you should replace ~ YOUR-GITHUB-USERNAME~ by your github username )
38
38
39
39
> git clone [email protected] :~YOUR-GITHUB-USERNAME~/metacpan-grep-front-end.git
@@ -42,10 +42,10 @@ You can then clone it locally (where you should replace ~YOUR-GITHUB-USERNAME~ b
42
42
43
43
The frontend is not using a database, but a ` git repo ` itself as a backend.
44
44
For this the production is using one huge git repository (~ 20 Go) indexing all the CPAN in one place !
45
- You can read more on this topic and find tools used to build this Git repo on the ( GitHub Repos) [ https://grep.metacpan.org/source-code ] page.
45
+ You can read more on this topic and find tools used to build this Git repo on the [ GitHub Repos] ( https://grep.metacpan.org/source-code ) page.
46
46
47
47
We do not want to use such a beast during development cycles, we only need a smaller version of it,
48
- you can simply clone it from this ( metacpan-cpan-extracted-lite) [ https://github.com/metacpan/metacpan-cpan-extracted-lite ] .
48
+ you can simply clone it from this [ metacpan-cpan-extracted-lite] ( https://github.com/metacpan/metacpan-cpan-extracted-lite ) .
49
49
It should be clone at the same level of * metacpan-grep-front-end* itself (do not clone it inside the repository).
50
50
51
51
# clone at the same level of metacpan-grep-front-end
@@ -121,7 +121,7 @@ From there you should be ready to
121
121
122
122
The project comes with a basic ` .travis.yml ` file.
123
123
124
- If you want to start smoking your own branches, you simply need to link your [ GitHub account] ( https://github.com )
125
- to your ( Travis CI account) [ https://travis-ci.org/ ] , then enable the repository in your ( Travis Dashboard) [ https://travis-ci.org/dashboard ]
124
+ If you want to start smoking your own branches, you simply need to link your [ GitHub account] ( https://github.com/ )
125
+ to your [ Travis CI account] ( https://travis-ci.org/ ) , then enable the repository in your [ Travis Dashboard] ( https://travis-ci.org/dashboard )
126
126
127
127
Note that any Pull Request submitted via GitHub would trigger a Travis smoke without any settings required from your side :-)
0 commit comments