Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/data/extract_declarations.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ As a side effect, this will pull down many other objects referenced
by fields that were referred to. For example ... XXX

If you wanted to pull out many objects from an org, it might be easier
to pull them out with with wildcards. There are wildcards for
to pull them out with wildcards. There are wildcards for
"all objects" (`OBJECTS(ALL)`), "all standard objects" (`OBJECTS(STANDARD)`),
and "all custom objects" (`OBJECTS(CUSTOM)`). For example, to pull out
all Account fields, all Standard Fields on Custom objects and all Custom
Expand Down
2 changes: 1 addition & 1 deletion docs/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ CumulusCI's `deploy` task uses the Metadata API to deploy metadata from the repo

Use the `path` option to specify the path to the metadata you wish to deploy. The metadata may be in either Metadata API or Salesforce DX source format. SFDX-format source will automatically be converted to Metadata API for deployment. This conversion takes place prior to application of transforms (below) and requires that the path be listed as a package directory in `sfdx-project.json`.

Set the test run level with the `test_level` option. Available values are `NoTestRun`, `RunLocalTests`, `RunAllTestsInOrg`, and `RunSpecifiedTests`. If you use `RunSpecifiedTests`, you must also supply a list of tests with the `specified_tests` option. This option accept a comma-separated value at the command line or a list in your `cumulusci.yml` markup.
Set the test run level with the `test_level` option. Available values are `NoTestRun`, `RunLocalTests`, `RunAllTestsInOrg`, and `RunSpecifiedTests`. If you use `RunSpecifiedTests`, you must also supply a list of tests with the `specified_tests` option. This option accepts a comma-separated value at the command line or a list in your `cumulusci.yml` markup.

## Source Transforms

Expand Down
2 changes: 1 addition & 1 deletion docs/dev.md
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,7 @@ referenced repository.
`cumulusci.yml` file. If found, recursively resolve those
dependencies and any dependencies belonging to them.

- Determine whether to install the project as as a managed package or unmanaged metadata:
- Determine whether to install the project as a managed package or unmanaged metadata:

: - If the project has a namespace configured in the
`cumulusci.yml` file, treat the project as a managed package
Expand Down
2 changes: 1 addition & 1 deletion docs/org_config-reference.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# org_config Object Reference

The `org_config` object can be used in the `cumulusci.yml` file to read a large number number of attributes of the Salesforce org currently used. For example, in a [custom flow step](https://cumulusci.readthedocs.io/en/stable/config.html#add-a-flow-step), you can use a `when` clause to adapt the behavior of the new step to the type of org (scratch org or not) by referencing the `org_config.scratch` attribute.
The `org_config` object can be used in the `cumulusci.yml` file to read a large number of attributes of the Salesforce org currently used. For example, in a [custom flow step](https://cumulusci.readthedocs.io/en/stable/config.html#add-a-flow-step), you can use a `when` clause to adapt the behavior of the new step to the type of org (scratch org or not) by referencing the `org_config.scratch` attribute.

The following information is documented here in the application's source code :
https://github.com/SFDO-Tooling/CumulusCI/blob/main/cumulusci/core/config/org_config.py
Expand Down
Loading