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
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -325,6 +325,18 @@ If you believe you've found an issue with Parse Server, make sure these boxes ar
325
325
326
326
-[ ] You've searched through [existing issues](https://github.com/ParsePlatform/parse-server/issues?utf8=%E2%9C%93&q=). Chances are that your issue has been reported or resolved before.
327
327
328
+
# Want to ride the bleeding edge?
329
+
330
+
The `latest` branch in this repository is automatically maintained to be the last
331
+
commit to `master` to pass all tests, in the same form found on npm. It is
332
+
recommend to use builds deployed npm for many reasons, but if you want to use
333
+
the latest not-yet-released version of parse-server, you can do so by depending
334
+
directly on this branch:
335
+
336
+
```
337
+
npm install parseplatform/parse-server.git#latest
338
+
```
339
+
328
340
# Contributing
329
341
330
342
We really want Parse to be yours, to see it grow and thrive in the open source community. Please see the [Contributing to Parse Server guide](CONTRIBUTING.md).
0 commit comments