Skip to content
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

Refactor 1: Seperate the business logic in different composite actions #17

Closed
Abhishek-kumar09 opened this issue Jun 7, 2023 · 1 comment · Fixed by #40
Closed

Refactor 1: Seperate the business logic in different composite actions #17

Abhishek-kumar09 opened this issue Jun 7, 2023 · 1 comment · Fixed by #40
Labels
code/refactor help wanted Extra attention is needed

Comments

@Abhishek-kumar09
Copy link
Contributor

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.

@Abhishek-kumar09 Abhishek-kumar09 changed the title Refactor 1: Seperate the business logic in difference composite actions Refactor 1: Seperate the business logic in different composite actions Jul 13, 2023
@Freedisch
Copy link
Contributor

@Abhishek-kumar09 , I will check this

@Freedisch Freedisch mentioned this issue Jul 27, 2023
1 task
@Chadha93 Chadha93 added the help wanted Extra attention is needed label Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/refactor help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants