Skip to content

Commit f85f16e

Browse files
committed
Fix broken links
1 parent 2292b8f commit f85f16e

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

community/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ The main [Gitter](https://gitter.im) room for Scala is:
5555

5656
Other, more specialized rooms include:
5757

58-
* **[scala/center](scala/center)**: for discussions about Scala community governance, processes, the Scala Platform, and projects going on at the Scala Center.
58+
* **[scala/center](https://gitter.im/scala/center)**: for discussions about Scala community governance, processes, the Scala Platform, and projects going on at the Scala Center.
5959
* **[scala/contributors](https://gitter.im/scala/contributors)**: for contributors to discuss work on changes to Scala.
6060
* **[scala/moocs](https://gitter.im/scala/moocs)**: for talking about the Scala Center's online courses
6161
* **[scala/job-board](https://gitter.im/scala/job-board)**: for employers and job seekers to connect with each other

contribute/codereviews.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ includeTOC: true
66
---
77
## Code Review Contributions
88

9-
In addition to [bug fixing](/contribute/guide/), you can help us review
9+
In addition to [bug fixing](/contribute/guide.html), you can help us review
1010
[waiting pull requests](#pull-requests-awaiting-comment).
1111
This is also a good (and recommended) way to get to know the feel of
1212
the bug-fixing and submissions process before jumping in with your
@@ -51,4 +51,4 @@ own pull requests.
5151
</div>
5252
</div>
5353

54-
Also note that the [Tools contributions](/contribute/tools/) page has more projects that will generate pull requests.
54+
Also note that the [Tools contributions](/contribute/tools.html) page has more projects that will generate pull requests.

contribute/guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ This is the impatient developer's checklist for the steps to submit a bug-fix pu
6161
3. [Fork the Scala repository](/contribute/hacker-guide.html#fork) and clone your fork (if you haven't already).
6262
4. [Create a feature branch](/contribute/hacker-guide.html#branch) to work on: use the branch name `issue/NNNN` where NNNN is the JIRA issue number.
6363
5. [Fix the bug, or implement the new small feature](/contribute/hacker-guide.html#implement), include new tests (yes, for bug fixes too).
64-
6. [Test, rinse](/contribute/hacker-guide.html#test) and [test some more](/contribute/partest-guide/) until [all the tests pass](/contribute/hacker-guide.html#verify).
64+
6. [Test, rinse](/contribute/hacker-guide.html#test) and [test some more](/contribute/partest-guide.html) until [all the tests pass](/contribute/hacker-guide.html#verify).
6565
7. [Commit your changes](/contribute/hacker-guide.html#commit) to your feature branch in your fork. Please choose your commit message based on the [Git Hygiene](https://github.com/scala/scala#user-content-git-hygiene) section of the Scala project README.
6666
8. If necessary [re-write git history](http://git-scm.com/book/en/Git-Branching-Rebasing) so that [commits are organized by major steps to the fix/feature](
6767
https://github.com/scala/scala#git-hygiene). For bug fixes, a single commit is requested, for features several commits may be desirable (but each separate commit must compile and pass all tests)

contribute/scala-standard-library-api-documentation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ component so that they show up in the correct issue filters.
7777
Please familiarize yourself with the following before contributing
7878
new API documentation to save time, effort, mistakes and repetition.
7979

80-
* [Forking the Repo](./hacker-guide.html#set-up) - follow the setup steps through
80+
* [Forking the Repo](./hacker-guide.html#2-set-up) - follow the setup steps through
8181
the Branch section. If providing new documentation related to an existing JIRA issue, use `issue/NNNN`
8282
or `ticket/NNNN` as the guide states. If providing API documentation with no associated
8383
JIRA issue, use `scaladoc/xxxx` instead.

documentation/getting-started-intellij-track/testing-scala-in-intellij-with-scalatest.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ There are multiple libraries and testing methodologies for Scala,
99
but in this tutorial, we'll demonstrate one popular option from the ScalaTest framework
1010
called [FunSuite](http://www.scalatest.org/getting_started_with_fun_suite).
1111

12-
We assume you know [how to build a project in IntelliJ]({{ site.baseurl }}documentation/getting-started-sbt-track/building-a-scala-project-with-intellij-and-sbt.html).
12+
We assume you know [how to build a project in IntelliJ]({{ site.baseurl }}/documentation/getting-started-intellij-track/building-a-scala-project-with-intellij-and-sbt.html).
1313

1414
## Setup
1515
1. Create an sbt project in IntelliJ.

0 commit comments

Comments
 (0)