Autoplan should only set commit status if it finds a project #954
Labels
feature
New functionality/enhancement
Comments
|
I'm seeing this as well. |
cket
added a commit
to cket/atlantis
that referenced
this issue
Mar 26, 2020
lkysow
pushed a commit
that referenced
this issue
Mar 29, 2020
franklad
added a commit
to franklad/atlantis
that referenced
this issue
Sep 9, 2021
`The Silence VCS Status` feature has been implemented in runatlantis#954. However there is no reference to it in the server side repo config. Add missing `The Silence VCS Status` `--silence-vcs-status-no-plans` in the reference for server side repo config.
nishkrishnan
pushed a commit
that referenced
this issue
Sep 9, 2021
`The Silence VCS Status` feature has been implemented in #954. However there is no reference to it in the server side repo config. Add missing `The Silence VCS Status` `--silence-vcs-status-no-plans` in the reference for server side repo config.
krrrr38
pushed a commit
to krrrr38/atlantis
that referenced
this issue
Dec 16, 2022
`The Silence VCS Status` feature has been implemented in runatlantis#954. However there is no reference to it in the server side repo config. Add missing `The Silence VCS Status` `--silence-vcs-status-no-plans` in the reference for server side repo config.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've been using Atlantis for a couple months now, it is a great tool!
One thing I have noticed is that Atlantis will add itself as a CI check to PRs even if they do not have any relevant code changes, resulting in a message saying
0/0 projects planned successfully. I think ideally developers would not see Atlantis on a PR unless autoplan finds projects to plan.In our use case this is very common since we want to use Atlantis in a monorepo that contains both Terraform and other unrelated code. I'm happy to contribute a PR for this if this would help others, let me know if I can clarify anything about the expected behavior.
The text was updated successfully, but these errors were encountered: