Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switched to apex-enterprise-patterns/setup-sfdx@v2 #95

Merged
merged 3 commits into from
Dec 20, 2023

Conversation

ImJohnMDaniel
Copy link
Collaborator

@ImJohnMDaniel ImJohnMDaniel commented Dec 19, 2023

This change is Reviewable

Copy link
Contributor

@daveespo daveespo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @ImJohnMDaniel and @stohn777)


.github/workflows/deploy.and.test.yml line 26 at r1 (raw file):

      # Setup the config parameters needed
      - run: sf config set target-dev-hub SFDX-ENV --global #Even though the setup-sfdx action uses --setdefaultdevhubusername, it doesn't seem to stick since it uses --setdefaultusername so we brute force it here
      # Create the scratch org

What's the reasoning with these rather uninformative comments in the YAML? Comments should only be used for unidiomatic code .. there's no mystery here as to what's going on

If you want to add the name property so that the log output in the GH UI is more palatable, that makes more sense ..

@ImJohnMDaniel
Copy link
Collaborator Author

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @ImJohnMDaniel and @stohn777)

.github/workflows/deploy.and.test.yml line 26 at r1 (raw file):

      # Setup the config parameters needed
      - run: sf config set target-dev-hub SFDX-ENV --global #Even though the setup-sfdx action uses --setdefaultdevhubusername, it doesn't seem to stick since it uses --setdefaultusername so we brute force it here
      # Create the scratch org

What's the reasoning with these rather uninformative comments in the YAML? Comments should only be used for unidiomatic code .. there's no mystery here as to what's going on

If you want to add the name property so that the log output in the GH UI is more palatable, that makes more sense ..

@daveespo, in my opinion, the comments help with the readability; nothing more.

stohn777
stohn777 previously approved these changes Dec 19, 2023
Copy link
Contributor

@daveespo daveespo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @ImJohnMDaniel)

@ImJohnMDaniel ImJohnMDaniel merged commit 2e6860d into master Dec 20, 2023
3 checks passed
@ImJohnMDaniel ImJohnMDaniel deleted the devops/update-to-sfv2-commands branch December 20, 2023 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants