-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pages starter workflow for Middleman #2145
base: main
Are you sure you want to change the base?
Conversation
|
This pull request has become stale and will be closed automatically within a period of time. Sorry about that. |
Going to reopen for future consideration. 🤔 |
@JamesMGreene updated this PR to correspond to your updates in #2244 |
@JamesMGreene any chance to get this merged? Middleman is one of the most well-known and used (over 5M downloads) static site generators in the Ruby ecosystem (probably the second one, after Jekyll, since Slate is built on top of Middleman): (source: https://jamstack.org/generators/) So having an official starter-workflow would be really really appreciated 🙏🏼 Thanks! |
This pull request has become stale and will be closed automatically within a period of time. Sorry about that. |
@JamesMGreene friendly ping! I still think Middleman is a relevant static generator in the Ruby community (Top 2 in popularity), so an official starter would be much much appreciated. |
Just like in #2255 (comment), unfortunately, we are not accepting new starter workflows for Pages at the moment. |
Pre-requisites
Please note that at this time we are only accepting new starter workflows for Code Scanning. Updates to existing starter workflows are fine.
Tasks
For all workflows, the workflow:
.yml
file with the language or platform as its filename, in lower, kebab-cased format (for example,docker-image.yml
). Special characters should be removed or replaced with words as appropriate (for example, "dotnet" instead of ".NET").GITHUB_TOKEN
so that the workflow runs successfully.For CI workflows, the workflow:
ci
directory.ci/properties/*.properties.json
file (for example,ci/properties/docker-publish.properties.json
).push
tobranches: [ $default-branch ]
andpull_request
tobranches: [ $default-branch ]
.release
withtypes: [ created ]
.docker-publish.yml
).For Code Scanning workflows, the workflow:
code-scanning
directory.code-scanning/properties/*.properties.json
file (for example,code-scanning/properties/codeql.properties.json
), with properties set as follows:name
: Name of the Code Scanning integration.creator
: Name of the organization/user producing the Code Scanning integration.description
: Short description of the Code Scanning integration.categories
: Array of languages supported by the Code Scanning integration.iconName
: Name of the SVG logo representing the Code Scanning integration. This SVG logo must be present in theicons
directory.push
tobranches: [ $default-branch, $protected-branches ]
andpull_request
tobranches: [ $default-branch ]
. We also recommend aschedule
trigger ofcron: $cron-weekly
(for example,codeql.yml
).Some general notes:
actions
organization, or