-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Introduce new mergeable
requirement
#385
Conversation
Codecov Report
@@ Coverage Diff @@
## master #385 +/- ##
=========================================
- Coverage 70.37% 69.58% -0.8%
=========================================
Files 62 62
Lines 3743 3797 +54
=========================================
+ Hits 2634 2642 +8
- Misses 922 967 +45
- Partials 187 188 +1
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #385 +/- ##
==========================================
- Coverage 70.37% 69.57% -0.81%
==========================================
Files 62 62
Lines 3743 3799 +56
==========================================
+ Hits 2634 2643 +9
- Misses 922 968 +46
- Partials 187 188 +1
Continue to review full report at Codecov.
|
I'll try and check this out tomorrow. |
@brndnmtthws I'm going to merge #386 to regen all the mocks and update pegomock. Can you then rebase off master please? Thanks! |
👍 |
Which VCS providers did you manually test this with? I can help you with testing, I just want to know. |
Just GitHub. However with all the code shuffling it would be a good idea for me to test it again before you merge this PR. |
723e71d
to
dc45f69
Compare
I've rebased on master and updated the PR. Also squashed all the commits into one. It looks like there are some style changes from my linter. I'm guessing that's because we're using a slightly different version. I can go through and drop those changes if necessary. Let me test this with GitHub and I'll report back. |
134bd94
to
2a6b2f5
Compare
Everything works, tested with GitHub: However there's an issue I've noticed, and I'd like to ask for guidance on: should the CLI override options remove any per-project options? Or should it be additive? Specifically, I'm referring to the logic here: https://github.com/brndnmtthws/atlantis/blob/2a6b2f50edb29545efda24a047ac71214e4a7680/server/events/project_command_runner.go#L218-L223 Currently the logic is additive, so it appends these requirements to the existing list. The downside of this is that it may check the same requirements multiple times if you specify it both per project, and globally. Should the global options override the project options? Thoughts? |
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.
In the middle of a review
To answer your question, the flags should override the yaml settings. When server-side config is released, the flags will be deprecated. |
3d37a6f
to
1945a5a
Compare
I think everything has been addressed, but you should probably take another look. |
I managed to test Bitbucket Server. We need to hit another endpoint and the response is different:
|
Hmm, should I guess we should be checking |
Something like this?: https://gist.github.com/brndnmtthws/d828c30fea582504c686845fb1b51cfa I'm not quite sure how to handle |
Patch looks great. Let's ignore vetoes, dunno either 😆 |
I think that's everything addressed, again. |
Introduce new `mergeable` requirement, in similar vein to the `approved` requirement. Ran `make go-generate` to update mocks accordingly. This addresses issue runatlantis#43.
I'm excited about this much-needed PR! It's a step in the right direction. Not to beat a dead horse, just want to emphasize that without something like Also, just to be clear, this PR addresses a big part of the issues raised. I'm just harping on the lack of security around |
Thanks for the awesome PR @brndnmtthws. I made some additional changes in #388 specifically around checking another field for github. |
Introduce new
mergeable
requirement, in similar vein to theapproved
requirement.
Addresses #43.