You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the RFC discussion there have been different features suggested that should consider for further iterations.
This issue lists them for intaking purposes
For a given PR raised by wge, as developer i want to be able to navigate both ways (from wge <-> git provider) with the context information required in order to act on the PR (merge or reject) where possible.
as app team using wge pipelines for my application, I want to understand how can i automatically merge created PRs, so I dont need to manually approve it under certain conditions
For one, the pipeline is not the ONLY way to push the new version, the user could manually edit the helmrelease(s) for a given environment. However, I do think a manual invocation of promoting is worth exploring (particularly when paired with a default strategy of waiting for all deployment targets within an environment to report success) - added Ability to manually invoke promotion to a given environment #1854
During the RFC discussion there have been different features suggested that should consider for further iterations.
This issue lists them for intaking purposes
For a given PR raised by wge, as developer i want to be able to navigate both ways (from wge <-> git provider) with the context information required in order to act on the PR (merge or reject) where possible.
as app team using wge pipelines for my application, I want to understand how can i automatically merge created PRs, so I dont need to manually approve it under certain conditions
as app team, I want to define whether promotions should create or update a pr when more than one change has been promoted but not merged. for example https://github.com/peter-evans/create-pull-request/blob/main/src/create-or-update-branch.ts
what to do when there is an urgent fix that we need to release and we cannot wait for the pipeline to run through all the environments
The text was updated successfully, but these errors were encountered: