[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-70694":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":16,"starSnapshotCount":16,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},70694,"starter-workflows","actions\u002Fstarter-workflows","actions","Accelerating new GitHub Actions workflows ","https:\u002F\u002Fgithub.com\u002Ffeatures\u002Factions",null,"TypeScript",11685,7088,578,271,0,13,42,113,39,120,"Other",false,"main",[7],"2026-06-12 04:00:56","\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F44036562?s=100&v=4\"\u002F> \n\u003C\u002Fp>\n\n## Starter Workflows\n\nThese are the workflow files for helping people get started with GitHub Actions.  They're presented whenever you start to create a new GitHub Actions workflow.\n\n**If you want to get started with GitHub Actions, you can use these starter workflows by clicking the \"Actions\" tab in the repository where you want to create a workflow.**\n\n\u003Cimg src=\"https:\u002F\u002Fd3vv6lp55qjaqc.cloudfront.net\u002Fitems\u002F353A3p3Y2x3c2t2N0c01\u002FImage%202019-08-27%20at%203.25.07%20PM.png\" max-width=\"75%\"\u002F>\n\n### Note\n\nThank you for your interest in this GitHub repo, however, right now we are not taking contributions. \n\nWe continue to focus our resources on strategic areas that help our customers be successful while making developers' lives easier. While GitHub Actions remains a key part of this vision, we are allocating resources towards other areas of Actions and are not taking contributions to this repository at this time. The GitHub public roadmap is the best place to follow along for any updates on features we’re working on and what stage they’re in.\n\nWe are taking the following steps to better direct requests related to GitHub Actions, including:\n\n1. We will be directing questions and support requests to our [Community Discussions area](https:\u002F\u002Fgithub.com\u002Forgs\u002Fcommunity\u002Fdiscussions\u002Fcategories\u002Factions)\n\n2. High Priority bugs can be reported through Community Discussions or you can report these to our support team https:\u002F\u002Fsupport.github.com\u002Fcontact\u002Fbug-report.\n\n3. Security Issues should be handled as per our [security.md](security.md)\n\nWe will still provide security updates for this project and fix major breaking changes during this time.\n\nYou are welcome to still raise bugs in this repo.\n\n### Directory structure\n\n* [agentic](agentic): solutions for Agentic starter workflows\n* [ci](ci): solutions for Continuous Integration workflows\n* [deployments](deployments): solutions for Deployment workflows\n* [automation](automation): solutions for automating workflows\n* [code-scanning](code-scanning): solutions for [Code Scanning](https:\u002F\u002Fgithub.com\u002Ffeatures\u002Fsecurity)\n* [pages](pages): solutions for Pages workflows\n* [icons](icons): svg icons for the relevant template\n\nEach workflow must be written in YAML and have a `.yml` extension. They also need a corresponding `.properties.json` file that contains extra metadata about the workflow (this is displayed in the GitHub.com UI).\n\nFor example: `ci\u002Fdjango.yml` and `ci\u002Fproperties\u002Fdjango.properties.json`.\n\n### Valid properties\n\n* `name`: the name shown in onboarding. This property is unique within the repository.\n* `description`: the description shown in onboarding\n* `iconName`: the icon name in the relevant folder, for example, `django` should have an icon `icons\u002Fdjango.svg`. Only SVG is supported at this time. Another option is to use [octicon](https:\u002F\u002Fprimer.style\u002Focticons\u002F). The format to use an octicon is `octicon \u003C\u003Cicon name>>`. Example: `octicon person`\n* `creator`: creator of the template shown in onboarding. All the workflow templates from an author will have the same `creator` field.\n* `categories`: the categories that it will be shown under. Choose at least one category from the list [here](#categories). Further, choose the categories from the list of languages available [here](https:\u002F\u002Fgithub.com\u002Fgithub\u002Flinguist\u002Fblob\u002Fmaster\u002Flib\u002Flinguist\u002Flanguages.yml) and the list of tech stacks available [here](https:\u002F\u002Fgithub.com\u002Fgithub-starter-workflows\u002Frepo-analysis-partner\u002Fblob\u002Fmain\u002Ftech_stacks.yml). When a user views the available templates, those templates that match the language and tech stacks will feature more prominently.\n\n### Categories\n* Agentic\n* continuous-integration\n* deployment\n* testing\n* code-quality\n* code-review\n* dependency-management\n* monitoring\n* Automation\n* utilities\n* Pages\n* Hugo\n\n### Variables\nThese variables can be placed in the starter workflow and will be substituted as detailed below:\n\n* `$default-branch`: will substitute the branch from the repository, for example `main` and `master`\n* `$protected-branches`: will substitute any protected branches from the repository\n* `$cron-daily`: will substitute a valid but random time within the day\n\n## How to test templates before publishing\n\n### Disable template for public\nThe template author adds a `labels` array in the template's `properties.json` file with a label `preview`. This will hide the template from users, unless user uses query parameter `preview=true` in the URL.\nExample `properties.json` file:\n```json\n{\n    \"name\": \"Node.js\",\n    \"description\": \"Build and test a Node.js project with npm.\",\n    \"iconName\": \"nodejs\",\n    \"categories\": [\"Continuous integration\", \"JavaScript\", \"npm\", \"React\", \"Angular\", \"Vue\"],\n    \"labels\": [\"preview\"]\n}\n```\n\nFor viewing the templates with `preview` label, provide query parameter `preview=true` to the  `new workflow` page URL. Eg. `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo_name>\u002Factions\u002Fnew?preview=true`.\n\n### Enable template for public\nRemove the `labels` array from `properties.json` file to publish the template to public\n","actions\u002Fstarter-workflows 是一个旨在加速 GitHub Actions 工作流创建的项目。它提供了一系列预定义的工作流模板，覆盖了从持续集成、部署到代码扫描等多个场景，帮助用户快速上手GitHub Actions。这些模板使用YAML编写，并配有额外的元数据文件以增强用户体验。该项目非常适合那些希望简化自动化流程配置过程的开发者或团队使用，在新项目中引入自动化测试、构建及部署等操作时尤为有用。",2,"2026-06-11 03:33:39","high_star"]