fix: bind project var #46
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Fix
What Is the Current Behavior?
The parameter project for the create-release job just works with default value (SENTRY_PROJECT).
Steps to Reproduce
Set your .circleci/config.yml:
Run your job and you will see that
parameters.projectstill using SENTRY_PROJECT, that is the default value.What Is the Expected Behavior?
When project parameter is filled it should use the new value instead of SENTRY_PROJECT
Additional Context
It is related to this issue: #27
I'm working on a monorepo that have multiple projects, and this is why I need to change the var name used to create releases.
To fix it I'm just binding the project parameter when create-release is called create-release.