Use env-vars for secrets used during release for ORM and HR (Gradle builds) rather than Project properties #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uilds) rather than Project properties
beikov
approved these changes
Dec 12, 2024
yrodiere
approved these changes
Dec 12, 2024
…uilds) rather than Project properties
DavideD
reviewed
Dec 13, 2024
DavideD
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Use env-vars for secrets used during release for ORM and HR (Gradle builds) rather than Project properties
NOTE : ready for review, but draft as we need to coordinate changes in ORM and HR projects