Skip to content

Commit

Permalink
fix(release): properly use force-build option
Browse files Browse the repository at this point in the history
  • Loading branch information
ygrishajev committed Sep 27, 2024
1 parent c0bca17 commit 19c8723
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/release-app.yml
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ jobs:
force_build=""
if [[ "${{ github.event.inputs.force-build }}" == 'true' ]]; then
force_build="--forceBuild"
force_build="-f"
fi
npm run release -w apps/${{ github.event.inputs.app }} -- $pre_release $force_build --verbose --ci -r ${{ secrets.API_REGISTRY }}
4 changes: 3 additions & 1 deletion apps/deploy-web/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,4 +43,6 @@ App configurations, including environment variables, are located in the `src/con
### Sample Environment Variables
All environment variables required for the app, along with their expected structure and types, can be found in the `env/.env.sample` file. This sample file serves as a template for setting up your environment variables and ensures that all necessary variables are accounted for in each environment.

By organizing environment variables and configuration this way, we ensure a consistent, safe, and scalable approach to managing different deployment environments.
By organizing environment variables and configuration this way, we ensure a consistent, safe, and scalable approach to managing different deployment environments.

FOO

0 comments on commit 19c8723

Please sign in to comment.