-
Notifications
You must be signed in to change notification settings - Fork 1.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
--hide-prev-plan-comments
doesn't work if Github App name contains a period
#2695
Labels
bug
Something isn't working
Comments
I believe this is a duplicate of #1161 |
If it's separate, please open a PR. We'd be happy to merge it. :) |
--hide-prev-plan-comments
doesn't work if Github App name contains a comma
Do you mean a comma |
Thank you for sharing the nearest issue and editing the description. You are right. I think #2697 may solve these issues. |
--hide-prev-plan-comments
doesn't work if Github App name contains a comma--hide-prev-plan-comments
doesn't work if Github App name contains a period
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
Overview of the Issue
When create GitHub app which contains
.
,--hide-prev-plan-comments
option never works fine.Becasue GitHub uses app name as
atlantis.app
and identifier isatlantis-app
like a following.Reproduction Steps
.
e.g.atlantis.app
--gh-app-slug=atlantis-app
--hide-prev-plan-comments
then
hide-prev-plan-comments
not works, because github pr comment usesatlantis-app[bot]
notatlantis.app[bot]
.If we use
--gh-app-slug=atlantis.app
, we got following error.Environment details
Atlantis server-side config file:
Additional Context
There are 2 solutions. When create
atlantis.app
GitHub app,--gh-app-slug=atlantis.app
and get app info fromhttps://api.github.com/apps/atlantis-app
nothttps://api.github.com/apps/atlantis.app
in the following code.atlantis/server/events/vcs/github_credentials.go
Line 104 in 020eeba
--gh-app-slug=atlantis-app
and convert username in the following code.atlantis/server/events/vcs/github_credentials.go
Lines 109 to 111 in 020eeba
The text was updated successfully, but these errors were encountered: