Fix old implicit reference to v3 repo #74
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iHiD
commented
Mar 2, 2021
|
It's the same for Creating an Representer and Creating a Test Runner |
|
Thanks. Want to PR those? :) |
|
No problem. |
loziniak
added a commit
to loziniak/docs-1
that referenced
this pull request
Mar 2, 2021
loziniak
added a commit
to loziniak/docs-1
that referenced
this pull request
Mar 2, 2021
| @@ -6,6 +6,8 @@ These are the steps to get going: | |||
|
|
|||
| 1. Check [our repository list for an existing `...-analyzer`](https://github.com/exercism?q=-analyzer) to ensure that one doesn't already exist. | |||
| 2. Scan the [contents of this directory](./) to ensure you are comfortable with the idea of creating an Analyzer. | |||
| 3. Open an issue at [exercism/exercism](https://github.com/exercism/exercism/issues/new) introducing yourself and telling us which language you'd like to create a Analayzer for. | |||
| 3. Open an issue at [exercism/exercism][exercism-repo] introducing yourself and telling us which language you'd like to create a Analayzer for. | |||
There was a problem hiding this comment.
Why not do:
Suggested change
| 3. Open an issue at [exercism/exercism][exercism-repo] introducing yourself and telling us which language you'd like to create a Analayzer for. | |
| 3. [Open an issue at exercism/exercism](https://github.com/exercism/exercism/issues/new) introducing yourself and telling us which language you'd like to create a Analyzer for. |
There was a problem hiding this comment.
Two reasons:
- Your other PR said we shouldn't use internal links, so I moved it to the end of the file 😛
- I figured we might have more info at the apex of the exercism/exercism directory, and possibly have issue templates and things so that it might be better to send someone to the apex. But I can be persuaded either way on this.
There was a problem hiding this comment.
- True :)
- It would be really nice to have an issue template. That is something we should do at some point. Feel free to merge as is. I'll approve.
ErikSchierboom
approved these changes
Mar 2, 2021
iHiD
pushed a commit
that referenced
this pull request
Mar 18, 2021
iHiD
pushed a commit
that referenced
this pull request
Mar 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.