Automate pr flow #2802
Merged
Automate pr flow #2802
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The goal of this plan is to enforce changes in the branching and deployment strategy for Atlan repositories. The new approach involves treating the staging branch as pre-prod, syncing staging to the main branch, and implementing a specific process for microservice repositories.The objective is to implement an automated workflow that facilitates the seamless promotion of changes from the staging branch to the main branch in the Atlan Helm repository. This automation aims to enhance efficiency, reduce manual intervention, and maintain a consistent deployment process for Helm charts.
:documentation: Link: https://www.notion.so/atlanhq/Automate-PR-flow-Plan-on-Atlan-Helm-Repository-099754761ce34a45bef68b4fa88e22ee