You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# renovate-config-algolia
2
2
3
-
This repository holds a [Renovate shareable configuration](https://renovateapp.com/docs/configuration-reference/config-presets), much like [algolia/eslint-config-algolia](https://github.com/algolia/eslint-config-algolia/).
3
+
This repository holds a [Renovate shareable configuration](https://docs.renovatebot.com/config-presets/), much like [algolia/eslint-config-algolia](https://github.com/algolia/eslint-config-algolia/).
4
4
5
-
[Renovate](https://renovateapp.com/) keeps npm dependencies up-to-date the right way, the right features and right time.
5
+
[Renovate](https://www.mend.io/renovate/) keeps npm dependencies up-to-date the right way, the right features and right time.
6
6
7
7
## How to use it
8
8
@@ -12,21 +12,21 @@ If you have a **JavaScript application** (dashboard, static website generator),
The only difference between the two configurations is that an application will have its `devDependencies`_and_`dependencies` pinned.
28
28
While a JavaScript library will only have its `devDependencies` pinned.
29
-
Read the [Renovate docs, dependency pinning](https://renovatebot.com/docs/dependency-pinning/) to learn more.
29
+
Read the [Renovate docs, dependency pinning](https://docs.renovatebot.com/dependency-pinning/) to learn more.
30
30
31
31
You do not need to install `renovate-config-algolia`, as it's automatically picked up by Renovate.
32
32
@@ -41,6 +41,6 @@ It will directly push to the GitHub default branch of your project.
41
41
42
42
It runs every weekend, Paris time.
43
43
44
-
We chose to have a configuration that directly pushes to GitHub to avoid any notification noise inside GitHub by having a lot of Pull Requests to merge manually.
44
+
We chose to have a configuration that directly merges PRs to avoid having a lot of Pull Requests to merge manually.
45
45
If the update passes your test suite, then it's merged directly.
46
-
If tests are not passing or if there's a major upgrade then a pull request will be opened.
46
+
If tests are not passing or if there's a major upgrade then the pull request will stay opened.
0 commit comments