[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-572758-105":53,"doc-detail-572758-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","actions-cheat-sheet-github-actions-workflow-setup-guide","Actions Cheat Sheet - GitHub Actions workflow setup guide","","Actions Cheat Sheet covers GitHub Actions workflow automation fundamentals, explaining how to compose reusable actions into custom CI/CD pipelines. It details workflow YAML structure (.yml/.yaml in .github/workflows), how events trigger runs, and how to configure branches/tags and path filters. The guide also describes jobs and steps, including runners (runs-on), dependencies (needs), containers, environment variables and secrets, services, and execution limits like timeout-minutes.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/actions-cheat-sheet-github-actions-workflow-setup-guide/572758/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/actions-cheat-sheet-github-actions-workflow-setup-guide/572758.png","ImageObject",442,249,{"name":88,"@type":89},"Dipper","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-10-13",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Where must GitHub Actions workflow YAML files be stored and what extension is required?","Question",{"text":108,"@type":109},"Workflow files use YAML syntax and must use a .yml or .yaml extension. Store them under the .github/workflows/ directory in the repository.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the on trigger control when a workflow runs?",{"text":113,"@type":109},"The on section defines the event type that triggers the workflow, and it can be configured to include or exclude specific branches, tags, and paths. It can also schedule runs using cron.",{"name":115,"@type":106,"acceptedAnswer":116},"What roles do jobs, needs, runs-on, and steps play in a workflow?",{"text":117,"@type":109},"A workflow run consists of jobs, identified by job_id. Jobs run in parallel by default unless needs specifies dependencies. runs-on selects the virtual host or self-hosted runner, while steps are the tasks within a job that run commands or actions.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},572758,1792338358,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":73,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":9},1374404997633,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","Actions Cheat Sheet  \nGitHub Actions give you the flexibility to build automated software development lifecycle workflows. You can write individual tasks, called actions, and combine them to create custom workflows in your repository. GitHub Actions are automated processes allowing you to build, test, package, release, or deploy any code project on GitHub, but you can also use them to automate any step of your workflow: merging pull requests, assigning labels, triaging issues to name a few.  \nWorkflow Syntax  \nWorkflow files use YAML syntax, and must have either a .yml or .yaml file extension. You must store workflow files in the.github/workflows/ directory of your repository. Each different YAML file corresponds to a different workflow.  \nname: My Workflow  \non:  \npush:  \nbranches:  \n- 'releases/*'  \n- '!releases/**-alpha'env:  \nmessage: 'conversation'  \nmy_token: ${{ secrets .GITHUB_TOKEN }} jobs:  \nmy_build:  \nruns-on: ubuntu-latest  \nsteps:  \n- name: Checking out our code uses: actions/checkout@master  \n- name: Say something  \nrun: |  \necho \"A little less ${message}\"  \necho \"A little more action\"my_job:  \nneeds: my_build  \ncontainer:  \nimage: node:10.16-jessie  \nenv:  \nNODE_ENV: development  \nports:  \n- 80 volumes:  \n- my_docker_volume:/volume_mount options: - -cpus 1  \nservices:  \nredis:  \nimage: redis  \nports:  \n- 6379/tcp  \nWorkflow name  \nThe name of your workflow will be displayed on your repository’s actions page.  \nWorkflow, Job or Step env  \nA map of environment variables which can be set at different scopes. Several environment variables are available by default (GITHUB_SHA, GITHUB_REF, GITHUB_EVENT_NAME, HOME, GITHUB_EVENT_PATH…) as well as a secret, GITHUB_TOKEN, which you can leverage for API calls or git commands through the secrets context.  \non Event  \nThe type event that triggers the workflow. You can provide a single event string, an array of events, or an event configuration map that restricts the execution of a workflow:  \n When using the push and pull_request events, branches and tags allow to select or exclude (with the ! prefix) git references the workflow will run on, while paths specifies which files must have been modified in order to run the workflow.  \n If your rules are only made of exclusions, you can use branches-ignore, tags-ignore and paths-ignore. The  ignore form and its inclusive version cannot be mixed.  \n The types keyword enables you to narrow down activities (opened, created, edited…) causing the workflow to run. The list of available activities depends on the event.  \n A workflow trigger can also be scheduled:  \non:  \nschedule:  \n- cron: '*/15 * * * *'  \njobs Collection  \nA workflow run is made up of one or more jobs identified by a unique job_id (my_build or my_job) . Jobs run in parallel by default unless queued with the needs attribute. Each job runs in a fresh instance of the virtual environment specified by runs-on.  \nJob name  \nThe name of the job displayed on GitHub.  \nneeds  \nIdentifies any job that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue.  \nruns-on  \nThe type of virtual host machine to run the job on. Can be either a GitHub or self-hosted runner. Jobs can also run in user-specified containers (see: container) . Available GitHubhosted virtual machine types are ubuntu-latest, windowslatest, macOS-latest plus some other specific versions for each operating system, in the form of ubuntu-xx .xx, macOSxx .xx or windows-xxxx. To specify a self-hosted runner foryour job, configure runs-on in your workflow file with selfhosted runner labels. Example: [self-hosted, linux] .  \nActions Cheat Sheet  \ncontainer  \nInstead of running directly on a host selected with runs-on, a container can run any steps in a job that don’t already specify a container. If you have steps that use both script and container actions, t","cbCaikAiSHeSZZt9","https://ap.wps.com/l/cbCaikAiSHeSZZt9","pdf",136157,"English","# Workflow Syntax\n## Workflow files and locations\n# Workflow Triggers (on Event)\n## push and pull_request filters\n## scheduled triggers (cron)\n## event activity types\n# Jobs and Execution\n## jobs collection and job_id\n## needs dependencies\n## runs-on and runner types\n# Containers, Environment, and Services\n## container attributes and networking\n## env variables and secrets (GITHUB_TOKEN)\n## services for databases and caches\n# Steps and Actions\n## steps sequence and processes\n## step name and uses\n## with inputs for action.yml","[{\"question\":\"Where must GitHub Actions workflow YAML files be stored and what extension is required?\",\"answer\":\"Workflow files use YAML syntax and must use a .yml or .yaml extension. Store them under the .github/workflows/ directory in the repository.\"},{\"question\":\"How does the on trigger control when a workflow runs?\",\"answer\":\"The on section defines the event type that triggers the workflow, and it can be configured to include or exclude specific branches, tags, and paths. It can also schedule runs using cron.\"},{\"question\":\"What roles do jobs, needs, runs-on, and steps play in a workflow?\",\"answer\":\"A workflow run consists of jobs, identified by job_id. Jobs run in parallel by default unless needs specifies dependencies. runs-on selects the virtual host or self-hosted runner, while steps are the tasks within a job that run commands or actions.\"}]","Actions Cheat Sheet - GitHub Actions workflow setup guide | PDF",1791929150]