8000 Merge branch 'master' into guinaut-using-orbs-fix-1 · stackbuilders/circleci-docs@3132855 · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Apr 8, 2025. It is now read-only.

Commit 3132855

Browse files
Merge branch 'master' into guinaut-using-orbs-fix-1
2 parents 81e27b4 + 1c3bcac commit 3132855

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

jekyll/_cci2/creating-orbs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ While not strictly enforced, it is best practice when versioning your production
269269
* MINOR: when you add functionality in a backwards-compatible manner
270270
* PATCH: when you make backwards-compatible bug fixes
271271

272-
#### Using Orbs in Orbs and Register-Time Resolution
272+
#### Using Orbs Within Your Orb and Register-Time Resolution
273273

274274
You may use an ```orbs``` stanza inside an orb.
275275

jekyll/_cci2/orb-intro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ In the above example, two orbs are imported into your config, the [Slack orb](ht
2929

3030
If you find that there are no existing orbs that meet your needs, you may author your own orb to meet your specific environment or configuration requirements by using the [CircleCI CLI]({{ site.baseurl }}/2.0/local-cli/) as shown in the `circleci orb help` output below. Although this is more time-consuming than using the import feature, authoring your own orb enables you to create a world-readable orb for sharing your configuration.
3131

32-
```
32+
```nohighlight
3333
$ circleci orb help
3434
Operate on orbs
3535

jekyll/_cci2/using-orbs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Executors define the environment in which the steps of a job will be run. When y
7272

7373
When you declare an executor in a configuration outside of `jobs`, you can use these declarations for all jobs in the scope of that declaration, enabling you to reuse a single executor definition across multiple jobs.
7474

75-
Each executor definition includes the subset of the children keys of a `job` declaration related to setting the environment for a job to execute. This means it does not include `steps`. The subset can be one or more of the following keys:
75+
An executor definition has the following keys available (some of which are also available when using the `job` declaration):
7676

7777
* `docker`, `machine`, or `macos`
7878
* `environment`

0 commit comments

Comments
 (0)
0