Ashwin Sangem
b1b3ae86ee
* Added Cloudrail according to instructions and existing examples * Adding Cloudrail according to documentation and examples * Oops * Add original Fortify on Demand workflow * Update Fortify on Demand workflow * Update Fortify on Demand supported languages * Add 3rd-party GitHub Actions disclaimer * Sysdig Secure Inline Scan with SARIF report to starter workflows * Added some extra comments, Github Actions V2 and changed env vars * Reviews from PR #1110 * Adding 'Dockerfile' to category list * Update according to PR review comments * File renames as requested in PR comments * Revert "Azure Data Factory CI starter workflow (#1111)" (#1146) This reverts commit7f30309cce. * use env variables for user-set values (#1117) Co-authored-by: Josh Gross <joshmgross@github.com> * Apply suggestions from nickfyson's code review Co-authored-by: Nick Fyson <nickfyson@github.com> * removing "deployment" templates from sync-ghes (#1127) * Update code-scanning/properties/sysdig-scan.properties.json Co-authored-by: Nick Fyson <nickfyson@github.com> * Update code-scanning/properties/sysdig-scan.properties.json Co-authored-by: Nick Fyson <nickfyson@github.com> * Changed svg logo * Rename sysdig.svg to sysdig-scan.svg * Switched svg logo (again) for a better fit * Rename fortify.json to fortify.properties.json * Correct character-case of "c" in Cloudrail * AWS template also used Docker * trigger on push instead of release (#1157) Co-authored-by: Josh Gross <joshmgross@github.com> * Adding MobSF starter workflow * Adhering to pull request guidelines * python: update to use python 3.10 Signed-off-by: Rui Chen <rui@chenrui.dev> * Added new templates for 3 clouds. * Revert "Added new templates for 3 clouds." This reverts commitc765d6316f. * Add ruby and update workflow * Add workflow for Microsoft C++ Code Analysis * Updated action to meet guidelines * quote the version strings * correct typo in msvc.properties.json * Update codeql.properties.json * Update code-scanning/properties/codeql.properties.json Co-authored-by: Arthur Baars <arthur@semmle.com> * Update codeql.properties.json * Update codeql.properties.json * Update code-scanning/mobsf.yml Co-authored-by: Nick Fyson <nickfyson@github.com> * Update code-scanning/properties/mobsf.properties.json Co-authored-by: Nick Fyson <nickfyson@github.com> * Fixed typo in workflow that will cause every run to fail * Update commit SHA * r: use setup-r@1 and include r@4 for starter (#1169) * r: use setup-r@1 and include r@4 for starter Signed-off-by: Rui Chen <rui@chenrui.dev> * use sha instead of tag for external action Co-authored-by: Josh Gross <joshmgross@github.com> Co-authored-by: Josh Gross <joshmgross@github.com> * elixir: refresh dependencies (#1212) - setup action got renamed into `setup-beam` - update elixir and erlang versions Co-authored-by: Yoni Leitersdorf <y@indeni.com> Co-authored-by: Ruud Senden <ruud.senden@microfocus.com> Co-authored-by: Ruud Senden <8635138+rsenden@users.noreply.github.com> Co-authored-by: Manuel Boira Cuevas <manuel.boira@MacBook-Pro.local> Co-authored-by: manuelbcd <manuel.boira@sysdig.com> Co-authored-by: Nick Fyson <nickfyson@github.com> Co-authored-by: Sarah Edwards <skedwards88@github.com> Co-authored-by: Josh Gross <joshmgross@github.com> Co-authored-by: Aparna Ravindra <82894348+aparna-ravindra@users.noreply.github.com> Co-authored-by: manuelbcd <manuelbcd@gmail.com> Co-authored-by: Abir Majumdar <abirismyname@github.com> Co-authored-by: Rui Chen <rui@chenrui.dev> Co-authored-by: David Verdeguer <daverlo@github.com> Co-authored-by: Daniel Winsor <danwin@microsoft.com> Co-authored-by: David Verdeguer <47184891+Daverlo@users.noreply.github.com> Co-authored-by: Arthur Baars <arthur@semmle.com> Co-authored-by: Abir Majumdar <83433840+abirismyname@users.noreply.github.com> Co-authored-by: Marco Gario <marcogario@github.com> Co-authored-by: Andy McKay <andymckay@github.com>
Starter Workflows
These 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.
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.
Directory structure
- ci: solutions for Continuous Integration workflows.
- deployments: solutions for Deployment workflows.
- automation: solutions for automating workflows.
- code-scanning: starter workflows for Code Scanning
- icons: svg icons for the relevant template
Each 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).
For example: ci/django.yml and ci/properties/django.properties.json.
Valid properties
name: the name shown in onboarding. This property is unique within the repository.description: the description shown in onboardingiconName: the icon name in the relevant folder, for example,djangoshould have an iconicons/django.svg. Only SVG is supported at this time. Another option is to use octicon. The format to use an octicon isocticon <<icon name>>. Example:octicon personcreator: creator of the template shown in onboarding. All the workflow templates from an author will have the samecreatorfield.categories: the categories that it will be shown under. Choose at least one category from the list here. Further, choose the categories from the list of languages available here. When a user views the available templates, those templates that match the same language will feature more prominently.
Categories
- continuous-integration
- deployment
- testing
- code-quality
- code-review
- dependency-management
- monitoring
- Automation
- utilities
Variables
These variables can be placed in the starter workflow and will be substituted as detailed below:
$default-branch: will substitute the branch from the repository, for examplemainandmaster$protected-branches: will substitute any protected branches from the repository$cron-daily: will substitute a valid but random time within the day