Closed ByteMeAsap closed 1 month ago
think the same thing @chienandalu
Wrong repo?
@chienandalu , can you suggest appropriate repo for adding this module? I would be using this module as a dependent module for creating a module for logging gitlab commits,PRs as membership activities(refer https://github.com/OCA/vertical-association/pull/174)
I guess server-backend would be more appropiate. What do you think @pedrobaeza
I new repository may be created, like we have interface-github. Anyway, I think this module is very weak and should incorporate more things to be useful for anyone, apart from #174, which is not very related with Gitlab itself.
I new repository may be created, like we have interface-github. Anyway, I think this module is very weak and should incorporate more things to be useful for anyone, apart from #174, which is not very related with Gitlab itself.
@pedrobaeza So, should this module be kept as a part of this repo? or should we incorporate the features of this module in the other module for membership_activity?
I don't still understand the goal of the gitlab
module, and as said, it's very weak for a complete module, as it's not tied at all to Gitlab in any sense.
@pedrobaeza This module is a technical module it's not meant for the user to do anything. It's meant for other modules to use that need a gitlab connection. https://github.com/OCA/vertical-association/pull/174 is not related to gitlab, but we have created another module that logs / creates membership activity based on commits, pull requests (merge requests), opening issues etc etc. which we will also propose.
But yes this module is not supposed to be here I would suggest server-backend.
Created a PR in server-backend - https://github.com/OCA/server-backend/pull/311
This module does not provide a functionality by itself but a base model to implement gitlab related features