How to cut a list of modules?

asked me to cut out a list of modules that we created.
so I want to know what is the procedure to succeed in doing this?

What do you mean by cutting? If you just want to reduce the list of modules you can merge some modules into a single one.

I have this list of modules and I need to isolate everything that is:
“Foresight” in a github repository specific to the provident business modules.
health in a deport github special health profession
the rest of the code in a community repository
the goal is to provide access to the specific business repository according to the customer’s needs

User Analytics
Rider - Insurance
Amendment - Clauses
Rider - Set of Riders
Amendment - SEPA data management
Amendment - Modification of benefits
Amendment - Person
Amendment - Process
Amendment - Person Amendment Process
Amendment - Amendment Set Process
Amendment - Receipt
Amendment - Renewal
Amendment - Full Resumption of Contract
Amendment - Backup and recalculation of premiums
Commission - Insurance
Commission - Riders
Commission - Insurer slips
Commission - Wholesale Broker
Commission - Conveyor fees
Commission - Management of over-providers
Commission - Rules Engine
Commission - Checkout Rules Engine
Commission - Waiting accounting movement
Committee - ORIAS
Commission - Prepayment
Commission - Takeover
Accounting - Accounting aggregate
Accounting - Accounting balance by third party
Accounting - Payment suspense account
Accounting - Receipt payment suspense account
Accounting - Advanced payment setup
Accounting - Insurer invoices
Accounting - Management of outstanding payments
Accounting - Historization of receipts states
Accounting - Letter checks
Accounting - Reports
Contract - Risk analysis
Contract - Insurance
Contract - Capitalization
Contract - Clauses
Contract - Collective
Contract - Request for parts
Contract - Warranty Details
Contract - Set of contracts
Contract - Premium Waiver
Contract - Management of reminder letters
Contract - Statement Management
Contract - Statement Management (en)
Contract - SEPA management
Contract - Unpaid
Contract - Reduction of the contract
Contract - Coverage Amount
Contract - Revalued Coverage Amount
Contract - Compensating accounting movement
Contract - External Number
Contract - Payments
Contract - Client portfolio
Contract - Premium
Contract - Contract Set Bonus
Contract - Insurance premiums
Contract - Process on set of contracts
Contract - Receipt
Contract - Surrender of the contract
Contract - Insurer Reports
Contract - Renewal Rules
Contract - Distribution network
Contract - Subscription
Contract - Collective subscription
Contract - Suspension of direct debits
Contract - Suspension due to non-payment
Declination of inactive quotes
Borrower - Loan Modification Rider
Borrower - Full contract takeover addendum
Borrower - TAEA calculation
Borrower - Calculation of the average loan rate
Borrower - Receipt
Borrower - Claim
Scheduled Contract Events
Planned events
P&C - Product
Product Laboratory - Insurance
Product Laboratory - Clause
Product Laboratory - Eligibility conditions
Product Laboratory - Distribution on network - Couriers
Product Laboratory - Network Distribution
Product Laboratory
Foresight - Amendment
Foresight - Beneficiary clause
Foresight - Clauses
Pensions - Premiums
Provident - Claims
Receipts - Commission
Health - Amendment on persons (fr)
Health - Contract (en)

Then you just need to create the required repositories and move your code there.

can you give me more details ?

First of all you need to bring each of your projects under git SCM control. There are many tutorials how to do this, jsut search the internet.
Then you need to setup organisations at github, create a repo for each of the projects at github and push your local git repo there.

Some notes:

  • It might be easier to use instead of github since gitlab allows structuring groups hierarchically. Thus a single top-level organisation/group would suffice.
  • Tryton uses heptapod, which is a fork of gitlab supporting mercurial (and git). When using gitlab it’s much easier to move to heptapod later, since the CI would be the same. (Whereas these github actions only work on github.)
  • Please think about using mercurial instead of git, since Tryton uses mercurial and this would ease collaboration.
  • Even when staying with git, you could create your repos at heptapod as it supports git, too.
  • There are plans for creating a place for ”contrib modules”, which will be at heptapod most propobly. THus using heptapod and mercurial might ease collaboration again.