Skip to content

Environment variables misspelled in README #3

@trevorsinnott

Description

@trevorsinnott

I believe the following environment variables are misspelled In the README.md:

  • line 89: FULL_PACAKGE_CREATION >> FULL_PACKAGE_CREATION
  • line 95: CI_SUCCESS_TAG = CI_DEPLOYED >> PROD_SUCCESS_TAG = PROD_DEPLOYED

Both suggested changes above are based on spelling in:

  • gscloudsolutions/GS-DevOps-Mate/Gitflow Workflow/MDAPI/bitbucket-pipelines.yml
  • gscloudsolutions/GS-DevOps-Mate/Gitflow Workflow/SFDX/bitbucket-pipelines.yml

GS-DevOps-Mate/README.md

Lines 89 to 95 in 27149bb

> **FULL_PACAKGE_CREATION:**
> This variable needs to be created only for the package creation where diff is not calculated based on the last successful deployment in the Target Org. Used in YAML.
> **MAJOR_VERSION, MINOR_VERSION, PATCH:**
> These three variables are also used to create a package version. Need to be created only for the package creation where diff is not calculated based on the last successful deployment in the Target Org. Used in YAML. You can check their usage in Gitflow Workflow YAMLs below.
> **GIT TAGS:**
> Only required if your Pipeline relies on Git Tags to create a diff based package. Based on your orgs you should have a different Git Tag for each org like
> CI_SUCCESS_TAG = CI_DEPLOYED, QA_SUCCESS_TAG = QA_DEPLOYED, UAT_SUCCESS_TAG = UAT_DEPLOYED etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions