Transform the monorepo

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!

dev/ci/test/README.md

@@ -66,3 +66,4 @@ All commands should be wrapped into a bach script, which is run as part of the `
       cd /sourcegraph
       ./dev/ci/test/new-vagrant-test/test.sh
 ```
+Hello Hello!

dev/depgraph/README.md

@@ -44,3 +44,4 @@ This command ensures the following lint passes. Violations of the lint rules wil
 - **NoLooseCommands**: Report main packages outside of known command roots
 - **NoReachingIntoCommands**: Report packages that import code from an unrelated command
 - **NoUnusedSharedCommandCode**: Report packages that could be moved into an internal package
+Hello Hello!

dev/gqltest/README.md

@@ -83,3 +83,4 @@ Adding new tests to this test suite is as easy as adding a Go test, here are som
   - Delete external services created during the test.
   - Although, sometimes you would not want to delete an entity so you could login and inspect the failure state.
 - Prefix your branch name with `backend-dry-run/` will run integration tests in CI on your pull request.
+Hello Hello!

dev/prometheus/README.md

@@ -5,3 +5,4 @@ This directory contains configuration for the [Prometheus](https://prometheus.io
 This directory is mounted into the `prometheus` container. After making your changes to this directory,
 simply `docker restart prometheus` for your changes to take effect (depending on your change, Prometheus
 may respond to it as soon as you save the file).
+Hello Hello!

dev/release/README.md

@@ -12,3 +12,4 @@ yarn run release help # add 'all' to see test commands as well
 
 Before using this tool, please verify that the [release configuration](./release-config.jsonc)
 is set up correctly.
+Hello Hello!

dev/sg/README.md

@@ -360,3 +360,4 @@ sg tail-log http
 # Tail all logs
 sg tail-log all
 ```
+Hello Hello!

dev/sg/root/README.md

@@ -1 +1,2 @@
 TODO: Move me into some shared area. This code is also used in dev/depgraph
+Hello Hello!

dev/tilt/README.md

@@ -30,3 +30,4 @@ Tilt will start an initial build of the frontend and deploy it. Whenever you are
 Similar to the `frontend` you can add other `custom_build` statements to your `Tiltfile` to build and watch the other servers.
 
 There are many `Tiltfile` modifications that can help accelerate the edit/build/deploy cycle: https://docs.tilt.dev/example_go.html
+Hello Hello!

dev/zoekt/README.md

@@ -4,3 +4,4 @@ This directory contains utilities that are useful for Zoekt development.
 
 - [update](./update) Updates the version of zoekt in `go.mod`.
 - [wrapper](./wrapper) Is used by our dev Procfile to control behaviour.
+Hello Hello!

enterprise/README.md

@@ -8,3 +8,4 @@ This directory contains Sourcegraph Enterprise code.
 ## Dev
 
 See [Local development: For Sourcegraph employees](https://docs.sourcegraph.com/dev/local_development#for-sourcegraph-employees) for how to work on this code.
+Hello Hello!

enterprise/cmd/executor/README.md

@@ -3,3 +3,4 @@
 The executor service polls the public frontend API for work to perform. The executor will pull a job from a particular queue (configured via the envvar `EXECUTOR_QUEUE_NAME`), then performs the job by running a sequence of docker and src-cli commands. This service is horizontally scalable.
 
 See the [executor queue](../frontend/internal/executorqueue/README.md) for a complete list of queues.
+Hello Hello!

enterprise/cmd/frontend/internal/executorqueue/README.md

@@ -6,3 +6,4 @@ The executor-queue maintains the executor work queues. Executor instances poll f
 
 - The `codeintel` queue contains unprocessed lsif_index records
 - The `batches` queue contains unprocessed batch_spec_execution records
+Hello Hello!

enterprise/cmd/precise-code-intel-worker/README.md

@@ -1,3 +1,4 @@
 # Precise code intel worker
 
 The precise-code-intel-worker service converts LSIF upload file into Postgres data. This service is horizontally scalable.
+Hello Hello!

enterprise/cmd/server/README.md

@@ -1,3 +1,4 @@
 # Sourcegraph Server
 
 This directory contains the code which makes up the `sourcegraph/server` Docker image which runs Sourcegraph on a single node.
+Hello Hello!

enterprise/cmd/worker/README.md

@@ -1,3 +1,4 @@
 # Enterprise worker
 
 The enterprise worker supplements the OSS worker with additional enterprise-relevant background jobs.
+Hello Hello!

enterprise/dev/ci/README.md

@@ -13,3 +13,4 @@ go run ./enterprise/dev/ci/gen-pipeline.go | buildkite-agent pipeline upload
 ## Testing
 
 To test this you can run `env BUILDKITE_BRANCH=TESTBRANCH go run ./enterprise/dev/ci/gen-pipeline.go` and inspect the YAML output. To change the behaviour set the relevant `BUILDKITE_` environment variables.
+Hello Hello!

internal/cmd/ghe-feeder/README.md

@@ -1,3 +1,4 @@
 # GHE feeder tool
 
 Please see [Handbook entry](https://about.sourcegraph.com/handbook/engineering/distribution/tools/ghe_feeder).
+Hello Hello!

internal/cmd/init-sg/README.md

@@ -77,3 +77,4 @@ The format for the external service json file is as follows, multiple github ext
   }
 ]
 ```
+Hello Hello!

internal/cmd/precise-code-intel-tester/README.md

@@ -77,3 +77,4 @@ rm -rf testdata/indexes/
 ```
 
 Then rerun the testing steps described above (starting at `clone-and-index.sh`)
+Hello Hello!

internal/cmd/progress-bot/README.md

@@ -17,3 +17,4 @@ Usage of ./progress-bot:
 The `progress-bot` is deployed with [this GitHub action](../../../.github/workflows/progress.yml).
 
 In order to deploy a new version, first run `docker build -t sourcegraph/progress-bot .` and then `docker push sourcegraph/progress-bot`.
+Hello Hello!

internal/cmd/resources-report/README.md

@@ -42,3 +42,4 @@ This bot can be [configured in Slack](https://api.slack.com/apps/A013EETK25V) wi
 
 - GCP: Declare resource types to query in [`gcp.go`](./gcp.go)'s `gcpResources` variable.
 - AWS: Declare queries for resources as functions in [`aws.go`](./aws.go)'s `awsResources` variable.
+Hello Hello!

internal/cmd/search-blitz/README.md

@@ -50,3 +50,4 @@ Logs are rotated every 10 mb.
 search-blitz calls the GraphQL API with a token of a dedicated user.
 
 Credentials: 1password.
+Hello Hello!

internal/cmd/tracking-issue/README.md

@@ -29,3 +29,4 @@ In order to deploy a new version, first run `docker build -t sourcegraph/trackin
 Run the tests with `go test`, update fixtures (i.e. GitHub issues and PRs data) with `go test -update.fixture` and update the generated tracking issue golden file with `go test -update`.
 
 You can also run the tool manually in `-dry` mode with `-verbose` output to visualize the resulting tracking issues without updating them on GitHub.
+Hello Hello!

internal/encryption/README.md

@@ -45,3 +45,4 @@ The `encryption.Key` interface was built to be simple, and intended to be extend
 - AWS KMS
 - Mounted Key
 - No Op
+Hello Hello!

internal/goreman/README.md

@@ -3,3 +3,4 @@ This is a fork of github.com/mattn/goreman at commit d0ee41b21be92ce6fd3e55ad11c
 This fork turns the command into a library.
 
 github.com/mattn/goreman is licensed as MIT.
+Hello Hello!

lib/README.md

@@ -3,3 +3,4 @@
 This directory is the root of a separate go module from the primary module rooted at sourcegraph/sourcegraph. This module exists to hold code that we want to reuse outside of the sourcegraph/sourcegraph repo.
 
 Code in this module should _not_ import from sourcegraph/sourcegraph or from other Sourcegraph repositories to avoid complicated dependency relationships. Instead consider moving code from elsewhere into this module.
+Hello Hello!

lib/codeintel/lsif/protocol/README.md

@@ -1,3 +1,4 @@
 # LSIF protocol utilities for Go
 
 This repository contains LSIF protocol struct definitions.
+Hello Hello!

lib/codeintel/tools/README.md

@@ -135,3 +135,4 @@ This command validates the output of an LSIF indexer. The following properties a
 ## lsif-visualize
 
 Documentation coming soon.
+Hello Hello!

schema/README.md

@@ -19,3 +19,4 @@ Sourcegraph uses the following JSON Schemas:
 ## Known issues
 
 - The JSON Schema IDs (URIs) are of the form `https://sourcegraph.com/v1/*.schema.json#`, but these are not actually valid URLs. This means you generally need to supply them to JSON Schema validation libraries manually instead of having the validator fetch the schema from the web.
+Hello Hello!