mirror of https://github.com/coder/code-server.git
Improve README callout to coder/coder (#6579)
This commit is contained in:
parent
7649b6e6ca
commit
6f078a48a6
|
@ -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`.
|
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.
|
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.
|
**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
|
each patch must result in a working code-server without any broken in-between
|
||||||
states otherwise they are difficult to test and modify.
|
states otherwise they are difficult to test and modify.
|
||||||
4. Add your changes to the patch (`quilt refresh`)
|
1. 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 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
|
reproduce the behavior it fixes or adds. Every patch should have an e2e test
|
||||||
as well.
|
as well.
|
||||||
|
|
||||||
|
|
|
@ -73,7 +73,7 @@ details.
|
||||||
Interested in [working at Coder](https://coder.com/careers)? Check out [our open
|
Interested in [working at Coder](https://coder.com/careers)? Check out [our open
|
||||||
positions](https://coder.com/careers#openings)!
|
positions](https://coder.com/careers#openings)!
|
||||||
|
|
||||||
## For Organizations
|
## For Teams
|
||||||
|
|
||||||
Want remote development for your organization or enterprise? Visit [our
|
We develop [coder/coder](https://cdr.co/coder-github) to help teams to
|
||||||
website](https://coder.com) to learn more about Coder.
|
adopt remote development.
|
||||||
|
|
|
@ -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).
|
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
|
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
|
After you sign up and create a new Google Cloud Provider (GCP) project, create a
|
||||||
new Compute Engine VM instance:
|
new Compute Engine VM instance:
|
||||||
|
|
Loading…
Reference in New Issue