Skip to content

Move exercises to subdirectory. Fixes #223 #224

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

Merged
merged 1 commit into from
Jan 22, 2016
Merged

Conversation

kytrinyx
Copy link
Member

No description provided.

@petertseng
Copy link
Member

Looks good, though I guess you could let someone look at it again after rebasing. All I really did here though was see that all the exercise dirs got moved and no dirs got moved that shouldn't have. I'm trusting y'all on the API allowing /exercises/ bit

@kytrinyx
Copy link
Member Author

Rebased.

@petertseng
Copy link
Member

Seems good to me. I think the build failure is a transient one? I don't know how to get travis to retry though. (Usually I just make an inconsequential change in my commit message and push again, that gets a retry going)

@kytrinyx
Copy link
Member Author

There's a 'restart build' button in travis that you should have access to (upper right corner).

retry

@kytrinyx
Copy link
Member Author

I kicked it off again. We'll see.

@petertseng
Copy link
Member

Confirmed I see that button. Guess the light coloring means I don't see it unless I know where to look for it. OK then.

@kytrinyx
Copy link
Member Author

Now it's a different one that broke. what the heck?

@kytrinyx
Copy link
Member Author

No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.

So it's stalling. It might just be graemlins in the travis CI system.

@kytrinyx
Copy link
Member Author

And green. OK, I think we're good to go.

petertseng added a commit that referenced this pull request Jan 22, 2016
Move exercises to subdirectory. Fixes #223
@petertseng petertseng merged commit 4f855bb into master Jan 22, 2016
@kytrinyx kytrinyx deleted the exercises-subdir branch January 22, 2016 22:48
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 16, 2017
the filepath needed used by example_gen.go was changed in exercism#224
the test cases were changed in this commit:
exercism/problem-specifications#463
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 16, 2017
the filepath needed used by example_gen.go was changed in exercism#224
the test cases were changed in this commit:
exercism/problem-specifications#463
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 16, 2017
the filepath used by example_gen.go was changed in exercism#224
README details on generating tests also updated to reflect moving
exercises into exercises subdirectory
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 16, 2017
fixes exercism#357

Since the re-organised exercises directory (exercism#224) the test generator
filepaths have been broken. This commit changes `gen.Gen` to take care
of locating the `canonical-data.json` file, allowing each exercises
`example_gen.go` file to just pass in the exercise name. This should
also help with any future changes that affect the filepaths.
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 16, 2017
the filepath needed used by example_gen.go was changed in exercism#224
the test cases were changed in this commit:
exercism/problem-specifications#463
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 16, 2017
the filepath needed used by example_gen.go was changed in exercism#224
the test cases were changed in this commit:
exercism/problem-specifications#463
robphoenix pushed a commit to robphoenix/exercism-go that referenced this pull request Jan 17, 2017
the filepath needed used by example_gen.go was changed in exercism#224
the test cases were changed in this commit:
exercism/problem-specifications#463
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants