First of all, thank you a lot for organizing such a great hackathon, I really do appreciate it!
Okay so now I have a doubt regarding the hackathon, the following paragraph is mentioned in the original post:
For this year’s hackathon, we’re encouraging participants to utilize existing GitHub Actions to create workflows that make sense in the real world. While you are free to create a new Action, the emphasis of this contest is to create practical and interesting solutions other developers can utilize to solve problems with open source.
Does this mean that workflows that use actions/Any_Action in their jobs are preferred than others that use custom-made actions such as shehab7osny/Any_Action, right? or does it mean to stick to the Actions currently available on the GitHub Actions' marketplace without the need to develop new ones?
The idea is you'll need to either create an Action or workflow FROM an existing Action (preferred), or create a new Action entirely. Look at what's on the Actions marketplace and build on one of those. Don't forget to write a blog post about it 😄
Hi @mishmanners
Thank you a lot for replying! I beg your pardon, but I find the phrase create an Action FROM an existing Action a little bit conflicting with the phrase in the original post utilize existing GitHub Actions to create workflows. As in your comment, it is suggested to create an Action while in the original post it is suggested to create a Workflow.
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”
So, am I supposed to create a Workflow from an existing Action or create an Action FROM an existing Action?
Hi @blackgirlbytes and @mishmanners
First of all, thank you a lot for organizing such a great hackathon, I really do appreciate it!
Okay so now I have a doubt regarding the hackathon, the following paragraph is mentioned in the original post:
For this year’s hackathon, we’re encouraging participants to utilize existing GitHub Actions to create workflows that make sense in the real world. While you are free to create a new Action, the emphasis of this contest is to create practical and interesting solutions other developers can utilize to solve problems with open source.
Does this mean that workflows that use actions/Any_Action in their jobs are preferred than others that use custom-made actions such as shehab7osny/Any_Action, right? or does it mean to stick to the Actions currently available on the GitHub Actions' marketplace without the need to develop new ones?
The idea is you'll need to either create an Action or workflow FROM an existing Action (preferred), or create a new Action entirely. Look at what's on the Actions marketplace and build on one of those. Don't forget to write a blog post about it 😄
Hi @mishmanners
Thank you a lot for replying! I beg your pardon, but I find the phrase
create an Action FROM an existing Actiona little bit conflicting with the phrase in the original postutilize existing GitHub Actions to create workflows. As in your comment, it is suggested to create an Action while in the original post it is suggested to create a Workflow.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”
So, am I supposed to create a Workflow from an existing Action or create an Action FROM an existing Action?
Thank you a lot for your help @blackgirlbytes and @mishmanners
I'm so sorry for any disturbance caused.
Feel free to create either one; an Action or a workflow. As long as it's new, and utilises an existing Action, and you write a blog post about it 😄