Skip to content

Commit 860f634

Browse files
Fix broken links on Swift Continuous Integration page (#885)
1 parent 916121a commit 860f634

File tree

1 file changed

+2
-2
lines changed
  • documentation/continuous-integration

1 file changed

+2
-2
lines changed

documentation/continuous-integration/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ layout: page
44
title: Swift Continuous Integration
55
---
66

7-
The Swift project follows an [incremental development model](../contributing/#contributing_code), and utilizes continuous integration (CI) testing of changes in pull requests before merging as a core tool for maintaining project stability. The system produces the snapshot builds posted on swift.org, and runs tests against active branches. It is also used as part of the review process to run tests against pull requests before committing them.
7+
The Swift project follows an [incremental development model](/contributing/#contributing-code), and utilizes continuous integration (CI) testing of changes in pull requests before merging as a core tool for maintaining project stability. The system produces the snapshot builds posted on swift.org, and runs tests against active branches. It is also used as part of the review process to run tests against pull requests before committing them.
88

99
## Configuration
1010

@@ -46,7 +46,7 @@ If there are issues found during testing, you will get a link to the details of
4646

4747
![CI Pass](../continuous-integration/images/ci_failure.png)
4848

49-
It is expected that changes meet the [quality standards](../contributing/#quality) for the Swift project before they are committed to the development branch, and you are responsible for fixing problems found by your changes. If your changes break builds or tests on the development or release branches, you will receive email notification.
49+
It is expected that changes meet the [quality standards](/contributing/#quality) for the Swift project before they are committed to the development branch, and you are responsible for fixing problems found by your changes. If your changes break builds or tests on the development or release branches, you will receive email notification.
5050

5151

5252
## Community Involvement

0 commit comments

Comments
 (0)