-
Notifications
You must be signed in to change notification settings - Fork 5.9k
doc: Switch screenshot to use Chrome #2422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
You can see the difference live here: https://github.com/cdr/code-server/tree/ss-20c2 |
7b2091a
to
0c9641c
Compare
Safari runs code-server horribly. We shouldn't even pretend that it sort of works. See the issues tagged browser-safari! Considered Firefox first but there's too many issues with it as well.
Not every PR needs our review. We get notified anyway as we're watching the repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Screenshot looks good, not sure what happened with .github/CODEOWNERS
@@ -1,3 +1 @@ | |||
* @code-asher @nhooyr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if removing CODEOWNERS here was intentional!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was! We strive to break down each PR into individual commits. Makes it much easier to review. See the justification in the second commit.
Creating a new PR for every little change tends to get unwieldy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But yea know what actually, I'll try to do that from now on. It's def confusing to mesh things together in unrelated PRs.
Safari runs code-server horribly. We shouldn't even pretend that it sort
of works.
See the issues tagged browser-safari!