- 1 Minute to read
- Print
- DarkLight
- PDF
How to turn on Actions and run your first Action (Quickstart)
- 1 Minute to read
- Print
- DarkLight
- PDF
![Screenshot 2024-03-28 at 2.49.51 PM.png ""](http://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/Screenshot 2024-03-28 at 2.49.51 PM.png)
CI/CD Actions quickstart
Actions requires the repository owner be an organization, not an individual. If you need to transfer a personal repository to an organization, please refer to How to transfer ownership of a repo.
Workflow files
Actions are defined in workflow.yml files.
Your repository needs one or more workflow files to trigger an Action workflow run.
Note: you must put workflow files in .allspice/workflows/
folder
Creating your first workflow file
Create a file in your repo .allspice/workflows/hello-world.yml
Select repository→Add File→New File
![new file file.png AllSpice demo file tab, at the bottom the add file drop-down menu is expanded. "New file" within the menu is circled in red along with the menu title, "add file".](http://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/new file file.png)
Name the file .allspice/workflows/hello-world.yml
Copy the following example workflow into the web text editor:
name: Workflow-hello-world
on:
push:
issues:
# Trigger on issue open, close, or reopen
types: [opened, closed, reopened]
jobs:
Job-Hello-World:
runs-on: ubuntu-latest
steps:
- name: "Print Hello World 🔎"
run: echo "Hello World"
After you have pasted the code block, click the “Commit Changes” button to commit the workflow file to the repository.
![creating actions hello world.png AllSpice demo in the new file tab in a repository. Code from above the image is pasted as the 18th line of code. Below the code is a commit changes section. At the very bottom there is a commit changes button in blue, and a cancel button in red.](http://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/creating actions hello world.png)
Trigger your first action
The example above should trigger an action as soon as you commit the files.
This workflow specifies that actions will trigger on push
or issue open/close
To trigger this action again do one of the following:
Push changes to the repo
Open/New issue (This is the easiest to check)
Close an issue
View Actions results
Visit the Actions tab and see the actions result
![actions tab(1).png AllSpice demos, actions tab open in a repository. Actions tab in circled in red.](http://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/actions tab(1).png)
Click on the workflow to see the results
![click on workflow.png AllSpice demo, actions tab is opened in a repsitory. An option to add workflow is in the tab, which is also circled.](http://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/click on workflow.png)
Click on your job step to see Hello World
![workflow click on jobs(2).gif AllSpice actions demo with action tab opened. To the left there is text that states "generalize server URL to current server with a green checkmark to its left. Underneath that is text stating "job-hello-world" with a green checkmark to its left. To the right of that is a gif in dark mode titled job-hello-world. Directly underneath the title it says success. There are 3 drop-down menus in the gif that are expanded and closed, which are "set up job", "print hello world", and "complete job".](http://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/workflow click on jobs(2).gif)
If something goes wrong, let’s troubleshoot!