Refactor 1: Seperate the business logic in different composite actions
Abhishek-kumar09 opened this issue · 1 comments
Abhishek-kumar09 commented
We are using composite github action to deal with different type of operations from running a script, calling action within the project, to calling another action from different source. To get all the benefits of composite nature of github action, it is required to separate some logic in its own github action yaml and reference from the main yaml.
Like, managing cypress could be one action, managing uploads to cloud another action and so on.
Freedisch commented
@Abhishek-kumar09 , I will check this