-
Notifications
You must be signed in to change notification settings - Fork 43
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 entity registration to GitLab provider #4331
Comments
JAORMX
added a commit
that referenced
this issue
Sep 9, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
This was referenced Sep 9, 2024
JAORMX
added a commit
that referenced
this issue
Sep 10, 2024
This is part of generalizing entity registration, as other providers will need to work with this mechanism. As part of the migration, this moved the logic to use our new entity model. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
10 tasks
JAORMX
added a commit
that referenced
this issue
Sep 10, 2024
This is part of generalizing entity registration, as other providers will need to work with this mechanism. As part of the migration, this moved the logic to use our new entity model. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 10, 2024
This adds a simple implementation of getting the name for an entity based on given properties. This also introduces the first properties for the GitLab provider, which are the group and project. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
10 tasks
JAORMX
added a commit
that referenced
this issue
Sep 11, 2024
This adds a simple implementation of getting the name for an entity based on given properties. This also introduces the first properties for the GitLab provider, which are the group and project. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 11, 2024
This is part of generalizing entity registration, as other providers will need to work with this mechanism. As part of the migration, this moved the logic to use our new entity model. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 11, 2024
This adds a simple implementation of getting the name for an entity based on given properties. This also introduces the first properties for the GitLab provider, which are the group and project. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This is part of generalizing entity registration, as other providers will need to work with this mechanism. As part of the migration, this moved the logic to use our new entity model. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This is part of generalizing entity registration, as other providers will need to work with this mechanism. As part of the migration, this moved the logic to use our new entity model. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This is part of generalizing entity registration, as other providers will need to work with this mechanism. As part of the migration, this moved the logic to use our new entity model. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
10 tasks
JAORMX
added a commit
that referenced
this issue
Sep 12, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 13, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 13, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 13, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 13, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 13, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
added a commit
that referenced
this issue
Sep 13, 2024
This allows us to use more general structures to handle repo registration as opposed to relying on the github-specific repo message. In the future, we'll have an `EntityService` that will work for any entity. But that's for another PR. Related-To: #4331 Signed-off-by: Juan Antonio Osorio <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe the enhancement
Solution Proposal
Describe alternatives you've considered
No response
Additional context
No response
Acceptance Criteria
No response
The text was updated successfully, but these errors were encountered: