-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Add a gist of the difference between code-server and Coder #4419
Add a gist of the difference between code-server and Coder #4419
Conversation
As told by @tmikaeld here: coder#3102 (reply in thread)
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.
This looks good to me!
I'll let @bpmct give the final 👍 |
Some checks are failing since some things like tokens are failing, what should fix that? |
Wait, why's this on the 3.12.2 milestone? This has to be on the 3.12.1 milestone, right? Or, will this be merged after 3.12.1? |
The Docs preview is broken for forks unfortunately so you can ignore that (we will fix hopefully soon). The Build/Pre-build shouldn't be failing though 🤔 I just re-ran it |
This makes no sense 🤔 @code-asher or @TeffenEllis any ideas why the Build is failing here
|
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.
Minor change + yarn fmt
Co-authored-by: Joe Previte <jjprevite@gmail.com>
Will do that soon, need to get my laptop out. |
Sorry for the delay @jsjoeio it will be here soon, I just had a bunch of problems with Gitpod, the main one being my email, so it took some time to straighten things up, but I did |
Here this is... Is this correct? |
@jsjoeio just curious... The README is in the docs, then how did you loop it into the repo homepage? I mean, that looks impossible, right? |
GitHub let's you put it at the root or in
|
Codecov Report
@@ Coverage Diff @@
## main #4419 +/- ##
=======================================
Coverage 66.04% 66.04%
=======================================
Files 30 30
Lines 1602 1602
Branches 315 315
=======================================
Hits 1058 1058
Misses 466 466
Partials 78 78 Continue to review full report at Codecov.
|
/ping @bpmct requesting review |
@im-coder-lg sorry, do you mind rebasing one more time? That should fix the e2e check and then I can merge! |
Wait, you mean running |
2021-11-06.09-16-05.mp4The video up there is the problem I have with And yeah, I am using Gitpod because my WIndows PC is slow. It is Windows 7, meaning I use Node 12. So I use Gitpod, and I switched from Node 16 to Node 14 via nvm as shown above. I have the latest yarn version but to no avail. Anybody, any ideas? |
No, rebasing so you have the latest changes from
But since you're on a fork, you'll probably ned to modify to |
I need to fix my brain. I am a Git pro but didn't know the simple thing called rebasing 😂 but thanks for explaining, I will try that now. Should I run |
lol no worries!
Nope, no need! Rebasing just get you in line with |
Looks like @code-asher is here to save the day! He turned on a feature that lets us use GitHub's UI to update your branch. As long as all CI passes, we should be good to merge! |
Kinda expected merging through GitHub but thought of using the CLI. I know the GitHub method but didn't understand rebasing fully. |
Ah, fixed! Now if the docs issue is fixed(or maybe not), then the PR is ready to be merged! |
So, about the docs, what should I do to fix it? I think if you gain access to the fork of mine, you could fix it. For now, I will try studying the Docs CI and find the issue out. |
Aha! The first issue here is: https://github.com/cdr/code-server/blob/94b2774f8c9fb120c19232d2739616e447f9b89d/.github/workflows/docs-preview.yaml#L28-L35 The logs in the checks page is: Run actions/checkout@v2
with:
repository: cdr/m
ref: refs/heads/master
submodules: true
fetch-depth: 0
ssh-strict: true
persist-credentials: true
clean: true
lfs: false
Error: Input required and not supplied: token The next issue is this: https://github.com/cdr/code-server/blob/94b2774f8c9fb120c19232d2739616e447f9b89d/.github/workflows/docs-preview.yaml#L72-L81 Console logs: Run ./ci/scripts/github_deployment.sh update
./ci/scripts/github_deployment.sh update
shell: /usr/bin/bash -e {0}
env:
GITHUB_DEPLOYMENT:
GITHUB_TOKEN: ***
DEPLOY_STATUS: skipped
DEPLOY_URL:
/home/runner/work/_temp/cf73eb14-f128-4001-941c-a1088042e7f8.sh: line 1: ./ci/scripts/github_deployment.sh: No such file or directory
Error: Process completed with exit code 127. The final one is this: Run marocchino/sticky-pull-request-comment@v2
with:
header: codercom-preview-docs
message: ✨ Coder.com for PR #4419 deployed! It will be updated on every commit.
* _Host_: /docs/code-server
* _Last deploy status_: skipped
* _Commit_: f25768a6c21c0ecf646204d3cdf74711f7182576
* _Workflow status_: https://github.com/cdr/code-server/actions/runs/1435646749
append: false
recreate: false
delete: false
hide_details: false
hide: false
hide_and_recreate: false
hide_classify: OUTDATED
GITHUB_TOKEN: ***
Error: Resource not accessible by integration How can we fix this other than adding the secret tokens(which I don't want to happen since it's a privacy leak of Coder)? Maybe if this persists, a maintainer only can finish this successfully. |
@im-coder-lg nice investigating! Yeah, it's documented here. I need to spend some time soon fixing this - sorry for all your trouble and thanks again for sending this PR |
Fixes #
Here @bpmct I did what I could. Looping in other people who need to review this:
@jsjoeio
@tmikaeld
And all maintainers.
Thanks to @tmikaeld for a small idea of the difference!