Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

treehouses/Lobby

People

Repo info

Activity

May 25 23:36

dependabot[bot] on npm_and_yarn

(compare)
May 25 23:36

dependabot[bot] closed #856
May 25 23:36

dependabot[bot] commented #856
May 25 23:36

dependabot[bot] labeled #857
May 25 23:36

dependabot[bot] opened #857
May 25 23:36

dependabot[bot] on npm_and_yarn

Bump grunt from 1.0.4 to 1.5.3 … (compare)
Apr 27 07:33

dependabot[bot] on npm_and_yarn

(compare)
Apr 27 07:33

dependabot[bot] closed #833
Apr 27 07:33

dependabot[bot] commented #833
Apr 27 07:33

dependabot[bot] labeled #856
Apr 27 07:33

dependabot[bot] opened #856
Apr 27 07:33

dependabot[bot] on npm_and_yarn

Bump grunt from 1.0.4 to 1.5.2 … (compare)
Apr 16 04:49

tuongtran23 forked
tuongtran23/treehouses.github.io
Apr 04 03:14

dogi closed #854
Apr 04 03:14

dogi on master

update vagranttutorial.md (fixe… (compare)
Apr 04 03:14

dogi closed #855
Apr 04 03:14

dogi commented #855
Apr 04 03:13

dogi edited #855
Apr 04 03:11

dogi synchronize #855
Apr 04 00:05

Mia-XXXX opened #855

RJ Padilla

@rjpadilla

Hey @/all I made a pull request treehouses/treehouses.github.io#805 that fixes issue treehouses/treehouses.github.io#800
Let me know what you think of those changes.

JLKwong

@JLKwong

My new router I ordered got delayed. :pensive: I'll just submit the issue tomorrow night with what I've found so far.

JLKwong

@JLKwong

I realized I haven't been tagging @all when I created issues. :sweat_smile: Here's some issues I submitted:
treehouses/treehouses.github.io#809
treehouses/treehouses.github.io#808
treehouses/treehouses.github.io#807
treehouses/treehouses.github.io#806
treehouses/treehouses.github.io#803
treehouses/treehouses.github.io#802

Issues are not required to be approved before a Pull Request is submitted for the respective fix; however, we do suggest that you wait until someone from the System Team confirms/approves the change that your issue addresses BEFORE you begin work on the fix.

Where on GitHub does it show whether someone from the System Team confirms/approves the change? I'm trying to work on the following issue:
treehouses/treehouses.github.io#652

BryanGazali

@BryanGazali

when the "ready" label is added, like here

BryanGazali

@BryanGazali

@JLKwong I approved your issue treehouses/treehouses.github.io#809

BryanGazali

@BryanGazali

@JLKwong I approved your issue treehouses/treehouses.github.io#807 treehouses/treehouses.github.io#802
treehouses/treehouses.github.io#803
please look at my comments treehouses/treehouses.github.io#808 treehouses/treehouses.github.io#806

RJ Padilla

@rjpadilla

So I figured out why I couldn't SSH as root to my pi on treehouses/treehouses.github.io#809 :

I didn't add my SSH key to my pi.
Glossed over the known_host fix when switching images on my pi.

Also kudos to the person who came up with adding ranger to treehouses.

BryanGazali

@BryanGazali

@rjpadilla please see my approval treehouses/treehouses.github.io#805 treehouses/treehouses.github.io#804

RJ Padilla

@rjpadilla

@BryanGazali Thanks!
Also do you think you can review my PR treehouses/treehouses.github.io#791 and tell me what you think?

JLKwong

@JLKwong

I'm trying to work on a branch copy to edit the page in treehouses/treehouses.github.io#809, but I honestly have no idea where the files for the the First Steps pages are? :sweat_smile: The closest I could find are the css and js folders in the following file path:
C:\Users\Ludory\JLKwong.github.io\mdwiki\extlib
But I can't find the HTML files. :pensive:

JLKwong

@JLKwong

I found one HTML file, but it doesn't seem to be it?
"C:\Users\Ludory\JLKwong.github.io\index.html"

BryanGazali

@BryanGazali

they're in the "pages" folder

JLKwong

@JLKwong

:relieved: :+1: Thank you so much.

BryanGazali

@BryanGazali

@rjpadilla please see my approval treehouses/treehouses.github.io#791

JLKwong

@JLKwong

Weird question, but I see 2 files for the same page. One is under the vi folder, and the other the blog folder. Should I edit both?

BryanGazali

@BryanGazali

edit the one in vi, the one in blog is a separate thing entirely

JLKwong

@JLKwong

:+1:

JLKwong

@JLKwong

My first (real) pull request :sob: :trophy::
treehouses/treehouses.github.io#810

JLKwong

@JLKwong

When working on a PR, how much am I allowed to deviate from the original proposed solution? Or should I follow it strictly? I'm working on adding the section described in this issue:
treehouses/treehouses.github.io#652

I wanted to keep the proposed solution's text, but format it so that the steps are in an ordered list for readability.

RJ Padilla

@rjpadilla

@JLKwong I don't think there is a consensus on how far you are allowed to deviate unless outlined by the organization. Anytime I make any additional changes from what is asked, I try to be explicit of these new changes in the PR's description. My pull request treehouses/treehouses.github.io#805 is an example in which I deviated a bit from the issue but was upfront on the additional changes inside of the description.

farzana184

@farzana184

@/all @dogi , I would like to add myself as a virtual intern. Can we set up a meeting?

JLKwong

@JLKwong

@rjpadilla Thank you for your advice. 🥺

JLKwong

@JLKwong

I made a pull request to add text for finding a Pi using the Advanced IP Scanner :relieved: :cherry_blossom: :
treehouses/treehouses.github.io#811

dogi

@dogi

awesome ... congrats

@farzana184 you can proceed to step 9

also watch the private messages

JLKwong

@JLKwong

I noticed that even when syncing my fork, there's a commit from a previous push that keeps lingering in my future commits. How do I remove unnecessary commits?

git status doesn't notice anything. GitHub itself says my branch is 2 commits ahead.

JLKwong

@JLKwong

My master branch is ahead of treehouses:master. How do I sync from treehouses:master?

Ludory@Ludory-Jostliz MINGW64 ~/JLKwong.github.io (master)
$ git status
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean

$ git pull https://github.com/treehouses/treehouses.github.io.git
From https://github.com/treehouses/treehouses.github.io

branch HEAD -> FETCH_HEAD
Already up to date.

JLKwong

@JLKwong

I figured it out. :relieved: :v:

This branch is even with treehouses:master.

I'm gonna create an issue using the advice from this resource I found:
https://github.community/t/syncing-a-fork-leaves-me-one-commit-ahead-of-upstream-master/1435

JLKwong

@JLKwong

I made a pull request to revise the markdown & GitHub resources:
treehouses/treehouses.github.io#814

RJ Padilla

@rjpadilla

@JLKwong If your <issues> branch is ahead by x commits then that is completely normal, but ...
... if its the master branch that's ahead you'll probably want to git reset or git revert.

RJ Padilla

@rjpadilla

... if its the master branch that's ahead you'll probably want to git reset or ~~git revert~~.

Don't use git revert on master, it will just make another commit.

JLKwong

@JLKwong

Thanks for the feedback. I'll include it as another option when I submit my issue.

JLKwong

@JLKwong

I made a pull request to rewrite the Vagrant tutorial to be less confusing to newcomers:
treehouses/treehouses.github.io#815

JLKwong

@JLKwong

I made a pull request to add header formatting to a couple sub-headings in the First Steps page:
treehouses/treehouses.github.io#816

BryanGazali

@BryanGazali

@JLKwong please see my approval treehouses/treehouses.github.io#816 treehouses/treehouses.github.io#813 treehouses/treehouses.github.io#812

JLKwong

@JLKwong

:relieved: :+1:

I made a pull request to add 2 commands to the Docker tutorial (docker start and docker stop):
treehouses/treehouses.github.io#817

JLKwong

@JLKwong

I made a pull request to add example images for watching and following in Step 0:
treehouses/treehouses.github.io#818

Chat via Matrix