jawills/Retrieve Salesforce Metadata
Retrieves Salesforce metadata and commits it to a branch
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| SFDX_AUTH_URL | The auth url tied to your deployment environment | yes | — |
| BRANCH_NAME | The name of the branch you want to backup the code to | yes | — |
| GITHUB_USER_NAME | Name tied to the git deployments | — | github-actions[bot] |
| GITHUB_USER_EMAIL | Email tied to the git deployments | — | github-actions[bot]@users.noreply.github.com |
| SOURCE_DIR | File paths for source to retrieve from the org. The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all source files in the directory and its subdirectories). | — | — |
| METADATA | Metadata component names to retrieve. Wildcards (`*`) supported as long as you use quotes, such as `ApexClass:MyClass*`. | — | — |
| MANIFEST_DIR | File path for the manifest (package.xml) that specifies the components to retrieve. If you specify this parameter, don't specify METADATA or SOURCE_DIR | — | — |
| IGNORE_CONFLICTS | Ignore conflicts and retrieve and save files to your local filesystem, even if they overwrite your local changes. This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as production orgs. | — | — |
| FORCE_PUSH | Force push commit to desired branch | — | — |
Outputs
no outputs