feat: Implement branch matching in repo-level config #2522
Merged
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
jamengual
added
feature
|
f.w.i.w., this is a re-incarnation of #1833 (I simply did not have time when eventually @jamengual responded). hopefully, this time we will be able to merge it. |
|
we will review as soon as we can @0x416e746f6e we are all really busy people sadly. |
|
Why "sadly"? Being very busy probably means being full-time employed => which is as very good thing for IT folks nowadays. :) |
|
touche |
|
@0x416e746f6e could you fix the conlficts? |
|
This was done @jamengual |
nitrocode
reviewed
Nov 5, 2022
nitrocode
approved these changes
Nov 5, 2022
|
@0x416e746f6e Thanks for the contribution |
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.
This PR adds the possibility to match branches in repo-level
atlantis.yamlconfig file.With this it becomes possible to use atlantis to deploy different projects for different base branches of the PR (for example: the PR towards
developbranch would deploy dev environment, while the PR towardsmainwould go into production).