Hi @mishmanners
Thank you a lot for organizing such an event. I really do appreciate it.
I already posted the following question in the Help Thread, but since this whole post is about my question, I would like to re-ask it with some in-depth details.
So, lets take the following GitHub Action for instance from the marketplace: actions/cache
Should I focus on developing a Workflow that is helpful for developers and include the actions/cache as it is mentioned in the main Hackathon post utilize existing GitHub Actions to create workflows? This would be something as below:
YAML file
- name: Cache Dependencies
uses: actions/cache@v2
Or should I focus on developing an Action based on the actions/cache as it is mentioned in this post create an Action FROM an existing Action? This would be something as below:
As the GitHub Actions Documentation states, Actions are individual tasks that you can combine to create jobs and customize your workflow.
On the other hand, Workflows are custom automated processes that you can set up in your repository to build, test, package, release, or deploy any project on GitHub
I'm so sorry for any disturbance caused but I just wanted to get some clarification before the submission. Your efforts are much appreciated.
Hi @mishmanners
Thank you a lot for organizing such an event. I really do appreciate it.
I already posted the following question in the Help Thread, but since this whole post is about my question, I would like to re-ask it with some in-depth details.
So, lets take the following GitHub Action for instance from the marketplace:
actions/cache
Should I focus on developing a Workflow that is helpful for developers and include the actions/cache as it is mentioned in the main Hackathon post
utilize existing GitHub Actions to create workflows
? This would be something as below:YAML file
Or should I focus on developing an Action based on the actions/cache as it is mentioned in this post
create an Action FROM an existing Action
? This would be something as below:YAML file
As the GitHub Actions Documentation states, Actions are
individual tasks that you can combine to create jobs and customize your workflow
.On the other hand, Workflows are
custom automated processes that you can set up in your repository to build, test, package, release, or deploy any project on GitHub
I'm so sorry for any disturbance caused but I just wanted to get some clarification before the submission. Your efforts are much appreciated.
You can do either 😄 it's up to you, as long as whatever you are creating is new, and you write a blog post on it.