From 6f078a48a639cce48d1016cce323940cac8122e5 Mon Sep 17 00:00:00 2001 From: Ammar Bandukwala Date: Tue, 12 Dec 2023 17:23:54 -0600 Subject: [PATCH] Improve README callout to coder/coder (#6579) --- docs/CONTRIBUTING.md | 8 ++++---- docs/README.md | 6 +++--- docs/requirements.md | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 41c72a80c..fcd755697 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -127,13 +127,13 @@ while quilt push; do quilt refresh; done 0. You can go through the patch stack with `quilt push` and `quilt pop`. 1. Create a new patch (`quilt new {name}.diff`) or use an existing patch. -2. Add the file(s) you are patching (`quilt add [-P patch] {file}`). A file +1. Add the file(s) you are patching (`quilt add [-P patch] {file}`). A file **must** be added before you make changes to it. -3. Make your changes. Patches do not need to be independent of each other but +1. Make your changes. Patches do not need to be independent of each other but each patch must result in a working code-server without any broken in-between states otherwise they are difficult to test and modify. -4. Add your changes to the patch (`quilt refresh`) -5. Add a comment in the patch about the reason for the patch and how to +1. Add your changes to the patch (`quilt refresh`) +1. Add a comment in the patch about the reason for the patch and how to reproduce the behavior it fixes or adds. Every patch should have an e2e test as well. diff --git a/docs/README.md b/docs/README.md index 9bb935b1a..b56f267e4 100644 --- a/docs/README.md +++ b/docs/README.md @@ -73,7 +73,7 @@ details. Interested in [working at Coder](https://coder.com/careers)? Check out [our open positions](https://coder.com/careers#openings)! -## For Organizations +## For Teams -Want remote development for your organization or enterprise? Visit [our -website](https://coder.com) to learn more about Coder. +We develop [coder/coder](https://cdr.co/coder-github) to help teams to +adopt remote development. diff --git a/docs/requirements.md b/docs/requirements.md index ad14c9f74..835fe5754 100644 --- a/docs/requirements.md +++ b/docs/requirements.md @@ -22,7 +22,7 @@ The following steps walk you through setting up a VM running Debian using Google Cloud (though you are welcome to use any machine or VM provider). If you're [signing up with Google](https://console.cloud.google.com/getting-started) for the first time, you should get a 3-month trial with -$300 of credits. +\$300 of credits. After you sign up and create a new Google Cloud Provider (GCP) project, create a new Compute Engine VM instance: