-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Add models for GitHub App #12070
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
Add models for GitHub App #12070
Conversation
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.
This doesn't have the code for creating/managing this right -- just the start of the modeling?
Get or create a GitHub app installation. | ||
|
||
Only the installation_id is unique, the target_id and target_type could change, | ||
but this should never happen. |
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.
Heh... foreboding.
# When an installation is deleted, we delete all its remote repositories | ||
# and relations, users will need to manually link the projects to each repository again. |
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.
Is there a nicer UI we can build for that in the future? Seems like a pretty large downside.
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.
Maybe something that facilitates re-connection in batch, maybe could be exposed as an API to start. But I only see this a problem for users with lots of repos connected, re-connection is straightforward, just select the repo from the settings and click save.
Yep, the service itself will be in the next PR. |
Since we have only one service with this type of integration, I didn't abstract this as a general attribute (like service_installation or similar), as we don't know if other services will ever bring something similar, and if they do, we don't know how they would implement it.
Extracted from #11942