Append Hello World to all README.md files

Author: Sourcegraph

README.md

@@ -62,3 +62,4 @@ The `doc` directory has additional documentation for developing and understandin
 Sourcegraph OSS is available freely under the [Apache 2 license](LICENSE.apache). Sourcegraph OSS comprises all files in this repository except those in the `enterprise/` and `client/web/src/enterprise` directories.
 
 All files in the `enterprise/` and `client/web/src/enterprise/` directories are subject to the [Sourcegraph Enterprise license](LICENSE.enterprise).
+Hello Hello!

cmd/frontend/README.md

@@ -7,3 +7,4 @@ Typically there are multiple replicas running in production to scale with load.
 Application data is stored in our PostgreSQL database.
 
 Session data is stored in the Redis store, and non-persistent data is stored in the Redis cache.
+Hello Hello!

cmd/github-proxy/README.md

@@ -3,3 +3,4 @@
 Proxies all requests to github.com to keep track of rate limits and prevent triggering abuse mechanisms.
 
 There is only one replica running in production.
+Hello Hello!

cmd/gitserver/README.md

@@ -36,3 +36,4 @@ gitserver's memory usage consists of short lived git subprocesses.
 This is an IO and compute heavy service since most Sourcegraph requests will trigger 1 or more git commands. As such we shard requests for a repo to a specific replica. This allows us to horizontally scale out the service.
 
 The service is stateful (maintaining git clones). However, it only contains data mirrored from upstream code hosts.
+Hello Hello!

cmd/query-runner/README.md

@@ -1,3 +1,4 @@
 # query-runner
 
 Periodically runs saved searches, determines the difference in results, and sends notification emails. It is a singleton service by design so there must only be one replica.
+Hello Hello!

cmd/repo-updater/README.md

@@ -1,3 +1,4 @@
 # repo-updater
 
 Repo-updater tracks the state of repos, and is responsible for automatically scheduling updates ("git fetch" runs) using gitserver. Other apps which desire updates or fetches should be telling repo-updater, rather than using gitserver directly, so repo-updater can take their changes into account. It is a singleton service by design, so there must only be one replica.
+Hello Hello!

cmd/searcher/README.md

@@ -5,3 +5,4 @@ Provides on-demand unindexed search for repositories. It scans through a git arc
 This service should be scaled up the more on-demand searches that need to be done at once. For a search the frontend will scatter the search for each repo@commit across the replicas. The frontend will then gather the results. Like gitserver this is an IO and compute bound service. However, its state is just a disk cache which can be lost at anytime without being detrimental.
 
 [Life of a search query](../../doc/dev/background-information/architecture/life-of-a-search-query.md)
+Hello Hello!

cmd/symbols/README.md

@@ -7,3 +7,4 @@ The ctags output is stored in SQLite files on disk (one per repository@commit).
 It is used by [basic-code-intel](https://github.com/sourcegraph/sourcegraph-basic-code-intel) to provide the jump-to-definition feature.
 
 It supports regex queries, with queries of the form `^foo$` optimized to perform an index lookup (basic-code-intel takes advantage of this).
+Hello Hello!

cmd/worker/README.md

@@ -1,3 +1,4 @@
 # Worker
 
 The worker service is a collection of the background jobs performed by a Sourcegraph instance. Jobs registered to the worker will run periodically or in response to some event read from the database.
+Hello Hello!

dev/auth-provider/README.md

@@ -23,3 +23,4 @@ If you need to edit client or user information and want to persist your changes:
 1.  Run `RESET=1 scripts/configure-keycloak.sh` to clobber the existing configuration with the `config/*.json` files' configuration.
 
 Not sure how to edit the JSON to achieve your desired outcome? Use the Keycloak admin interface at http://localhost:3220/auth (login as `root`/`q`) to change configuration, and then export to JSON.
+Hello Hello!