Skip to content

Commit 37d226d

Browse files
authored
Merge pull request jtarchie#191 from brunoban/fix-readme
Fix on Readme for Concourse links
2 parents 348d93d + 22a4a26 commit 37d226d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ resource only support *GITHUB*.
99

1010
## Deploying to Concourse
1111

12-
You can use the docker image by defining the [resource type](http://concourse.ci/configuring-resource-types.html) in your pipeline YAML.
12+
You can use the docker image by defining the [resource type](https://concourse-ci.org/resource-types.html) in your pipeline YAML.
1313

1414
For example:
1515

@@ -41,7 +41,7 @@ resource_types:
4141
linking to builds. On newer versions of Concourse ( >= v0.71.0) , the resource will
4242
automatically sets the URL.
4343

44-
This supports the [build environment](http://concourse.ci/implementing-resources.html#resource-metadata)
44+
This supports the [build environment](https://concourse-ci.org/implementing-resources.html#resource-metadata)
4545
variables provided by concourse. For example, `context: $BUILD_JOB_NAME` will set the context to the job name.
4646

4747
* `private_key`: *Optional.* Private key to use when pulling/pushing.
@@ -170,13 +170,13 @@ Set the status message for `concourse-ci` context on specified pull request.
170170
* `path`: *Required.* The path of the repository to reference the pull request.
171171

172172
* `status`: *Required.* The status of success, failure, error, or pending.
173-
* [`on_success`](https://concourse.ci/on-success-step.html) and [`on_failure`](https://concourse.ci/on-failure-step.html) triggers may be useful for you when you wanted to reflect build result to the PR (see the example below).
173+
* [`on_success`](https://concourse-ci.org/on-success-step-hook.html#on_success) and [`on_failure`](https://concourse-ci.org/on-failure-step-hook.html#on_failure) triggers may be useful for you when you wanted to reflect build result to the PR (see the example below).
174174

175175
* `context`: *Optional.* The context on the specified pull request
176176
(defaults to `status`). Any context will be prepended with `concourse-ci`, so
177177
a context of `unit-tests` will appear as `concourse-ci/unit-tests` on Github.
178178

179-
This supports the [build environment](http://concourse.ci/implementing-resources.html#resource-metadata)
179+
This supports the [build environment](https://concourse-ci.org/implementing-resources.html#resource-metadata)
180180
variables provided by concourse. For example, `context: $BUILD_JOB_NAME` will set the context to the job name.
181181

182182
* `comment`: *Optional.* The file path of the comment message. Comment owner is same with the owner of `access_token`.

0 commit comments

Comments
 (0)