-
Notifications
You must be signed in to change notification settings - Fork 56
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
Add variables with scope #697
Add variables with scope #697
Conversation
- Renaming an environment by using the API was deprecated in GitLab 15.9. - Renaming an environment with the API removed in GitLab 16.0.
…moved in GitLab 16.0 ...
'gitlab/gitlab-ee:16.6.2-ee.0' 'gitlab/gitlab-ee:16.11.1-ee.0'
…o feature/gitlab-16.11.1-ee.0
This reverts commit dca5ce8.
…..." This reverts commit f824d8d.
…tailedMergeStatus ...
Co-authored-by: Thomas Cortes <[email protected]>
Co-authored-by: Thomas Cortes <[email protected]>
…pproved by the maintainers ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the points stating that it's a breaking change: at the moment we try to avoid them.
We have an internal list of the breaking changes that would be neat to add in a further major version. Fields to properties and cleaning old or obsolete props and methods as well.
Separate two signatures in order to prevent breaking change ... Co-authored-by: Thomas Cortes <[email protected]>
environmentScope can't be null ... Co-authored-by: Thomas Cortes <[email protected]>
…to feature/variables-with-scope
@Toa741 Thanks again for the fabulous collaboration! |
At the moment it's only supported to read ci/cd-variables with scope, now they can be created, updated and deleted ...