Skip to content

update workflow #25

Merged
louisachu merged 1 commit intomainfrom
devsite-2002-update-workflow
Nov 19, 2025
Merged

update workflow #25
louisachu merged 1 commit intomainfrom
devsite-2002-update-workflow

Conversation

@louisachu
Copy link
Contributor

To update the workflow to only do prod and stage separately how commerce suggested.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

deployAll: ${{ inputs.deployAll }}
env: ${{ inputs.env || 'prod' }}
baseSha: ${{ inputs.baseSha || '' }}
deployAll: ${{ inputs.deployAll || true }}
Copy link
Contributor

@melissag-ensemble melissag-ensemble Nov 19, 2025

Choose a reason for hiding this comment

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

you should set default on line 25 instead.

is this a work-around for https://jira.corp.adobe.com/browse/DEVSITE-1972? otherwise, i'm not sure we want this checked by default, because it might overload EDS server

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it's a fallback that we can pick, this is from commerce

baseSha: ${{ inputs.baseSha }}
deployAll: ${{ inputs.deployAll }}
env: ${{ inputs.env || 'prod' }}
baseSha: ${{ inputs.baseSha || '' }}
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

same reason as above

env: ${{ inputs.env }}
baseSha: ${{ inputs.baseSha }}
deployAll: ${{ inputs.deployAll }}
env: ${{ inputs.env || 'prod' }}
Copy link
Contributor

@melissag-ensemble melissag-ensemble Nov 19, 2025

Choose a reason for hiding this comment

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

do we need this? it already defaults to prod on line 13

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is because if it's from a push event, the inputs can be not available at all, meaning it can be like a null or undefined, so it's needed to have a fallback

Copy link
Contributor

@melissag-ensemble melissag-ensemble left a comment

Choose a reason for hiding this comment

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

please see comments about defaults

@louisachu louisachu merged commit 822cb27 into main Nov 19, 2025
2 checks passed
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.

2 participants