deadlyvipers / dojo_rules Goto Github PK

Trying out hub on the command line.

To add a bit of a personal touch, add a programmer grievance of your own to the "kill_list.md" file.

I have followed the instructions and cannot figure out how to move past Q4 of section 2.2. There is nothing but master to pull from. Please help.

""Create a pull request from your branch to your master. When you create a pull request by default it'll go from your master branch back to "deadlyvipers/dojo_rules". In this case though, we want the pull request to go from "dojo_rules/deadly_skills" to "dojo_rules/master" – both in your repository.

To do this, create a pull request on GitHub. Make sure the base is your master and the "compare" is your "deadly_skills" branch. This should show all of the changes you made on your branch.""

I'm trying to add the Code School Kiddo as a collaborator but it's not working. I've removed access and requested access more than 8 times and it's still just waiting for a response. Is there a problem with it being overloaded?

NEw

We're going to need more weapons than we have

asdas

The list is only a small fraction of the rules we follow.

need more weapons

Added path information about me.

My folks tried to use this on IE3 and it didn't work - fix immediately!

Whether it's my command line converting to Vim or Git stating that merges need to be either committed or stashed -- again in Vim unless I use Git for Mac -- I'm running into the same problems over and over again despite my computer being able to communicate and pull down from Github, itself.

Creating the branches and tags through the Github interface is most likely nothing desired at this point in the course. I thought starting over with a newly forked, clean repository would help.

It hasn't.

Add Introduction

I am not receiving the new_rules branch. I can't seem to get it added to my repository. I added @codeschool-kiddo as a collaborator, but the Deadly Skills list was the last thing I was asked to do.

Why have I not received a response about this problem? I want to be able to continue with the project past this point. Is @codeschool-kiddo an automated account? If so, then you'd need to set up dependencies for certain actions on the client-side, but it also means that when the client-side fulfills what is asked of them, the server-side is supposed to react accordingly, correct?

May I please ask what's going on with this project? I keep getting stuck in completely random places for reasons that seem to be happening server-side. I really like and want to finish this project.

Could it be something I'm not doing properly, if so, please tell me what it is.

No new task assigned?

@deadlyvipers

Upon commiting and marking in commit notices "fixes #3" the the issue was not automatically closed.
Clicked on submit answer, and was presented with following, which did not allow me to continue.
Not able to continue as a result. (global email was set, and follow all steps, but error continues)

It appears that your user.email is not configured properly. Follow these steps to correct the issue.

First, set your global user.email config.

dojo_rules (kill_list)$ git config --global user.email [your GitHub account email address]

Next, you need to amend the commit so that the author is reset.

dojo_rules (kill_list)$ git commit --amend --reset-author --no-edit

Finally, push the amended commit to GitHub and try again.

dojo_rules (kill_list)$ git push origin kill_list -f

Sto provando a usare il test di http://campus.codeschool.com

dqwd

I created pull request, even two
#8636

But grader dont see it.

"No pull request was found on the dojo_rules repository. Make sure you're in your fork of the repo and do a pull request back to deadlyvipers/dojo_rules."

Why?

The instructions for the pull request portion of level 2, section 1 state that a pull request can be created within the confines of Github without the command line, but the instructions simply state 'select'

dojo_rules$ git push origin
dojo_rules (deadly_skills)$ git push origin

There is nothing stating or illustrating what looks like a command line directive. This directive is perplexing since it's not for the command line. What does it mean?

Not every

To add a bit of a personal touch, add a programmer grievance of your own to the "kill_list.md" file.

new issue2

To add a bit of a personal touch, add a programmer grievance of your own to the "kill_list.md" file.

I've "started over" at least six (6) times thus far, and I still receive the "Incorrect Submission: The closed pull request for deadly_skills could not be found. Double check that it has been merged and that it's pull request is closed."

I've forked https://github.com/codeschool-kiddo-level-2-complete/dojo_rules, added "codeschool-kiddo" as a Collaborator, cloned my fork to my local repo, performed a git add, commit && push; changed directory to the 'dojo_rules', git checkout (master), and performed the below listed commands--yet I'm still receiving the aforementioned "Incorrect Submission"

Please help...

Sincerely,

Cary Chapman

Find the deadly_skills merge commit, checkout it out, create the v1.2.0 tag, and push it to GitHub.

Check out master of dojo_rules.

dojo_rules$ git checkout master
Find the commit where deadly_skills was merged.

dojo_rules$ git log
Once you find the SHA-1 of the deadly_skills merge commit, check it out.

dojo_rules$ git checkout 15f59e89a42e6e1dcea997281c975863c6e2d861
Add tag v1.2.0 to this revision.

dojo_rules$ git tag -a v1.2.0 -m "Creating v1.2.0 tag."
Finally, push the tag to GitHub using –tags option.

dojo_rules$ git push origin --tags

I have used up all my hints, including the one that says to start over which I am finding it hard to take seriously, and still haven't resolved the situation. There is one thing that still escapes me: The 2nd hint (I think) says "This can be done entirely on the GitHub website..." and just below it is what appears to be a console with two commands:

dojo_rules$ git push_origin
dojo_rules (deadly_skills)$ git push origin

Not only does that fly in the face of the earlier statement but it is not clear to me how we would get those two prompts even were it not a non sequitur.

No matter how many times I restart the repository from scratch, part 3 regarding the tags and branches -- likely the releases, as well, since that's part of the chapter. I don't know what I'm doing wrong.

sdfds

To add a bit of a personal touch, add a programmer grievance of your own to the "kill_list.md" file.

From 8h to 9h.
Bring someone that you dislike to sparring.

How can I go on?