actions/starter-workflows
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'main' into add-msbuild-cpp-workflow

Browse Source
This commit is contained in:
Ben McMorran
2020-11-25 12:25:48 -08:00
committed by GitHub
parent 92d9a2c433 8c0ca1f934
commit 3f9a0a4044
12 changed files with 49 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/pull_request_template.md
+6 -5
View File
@@ -1,4 +1,4 @@
This repository contains configuration for what users see when they click on the `Actions` tab. This repository contains configuration for what users see when they click on the `Actions` tab and the setup page for Code Scanning.
It is not: It is not:
* A playground to try out scripts * A playground to try out scripts
@@ -6,7 +6,7 @@ It is not:
--- ---
**Please note that we are not accepting new starter workflows at this time. Updates to existing starter workflows are fine.** **Please note that at this time we are only accepting new starter workflows for Code Scanning. Updates to existing starter workflows are fine.**
--- ---
@@ -21,16 +21,17 @@ In the workflow and properties files:
- [ ] Include comments in the workflow for any parts that are not obvious or could use clarification. - [ ] Include comments in the workflow for any parts that are not obvious or could use clarification.
- [ ] CI workflows should run on `push` to `branches: [ $default-branch ]` and `pull_request` to `branches: [ $default-branch ]`. - [ ] CI workflows should run on `push` to `branches: [ $default-branch ]` and `pull_request` to `branches: [ $default-branch ]`.
- [ ] Packaging workflows should run on `release` with `types: [ created ]`. - [ ] Packaging workflows should run on `release` with `types: [ created ]`.
- [ ] Code Scanning workflows should run on `push` to `branches: [ $default-branch, $protected-branches ]` and `pull_request` to `branches: [ $default-branch ]`. We also recommend a `schedule` trigger of `cron: $cron-weekly`.
Some general notes: Some general notes:
- [ ] This workflow must only use actions that are produced by GitHub, [in the `actions` organization](https://github.com/actions), **or** - [ ] This workflow must only use actions that are produced by GitHub, [in the `actions` organization](https://github.com/actions), **or**
- [ ] This workflow must only use actions that are produced by the language or ecosystem that the workflow supports. These actions must be [published to the GitHub Marketplace](https://github.com/marketplace?type=actions). Workflows using these actions must reference the action using the full 40 character hash of the action's commit instead of a tag. Additionally, workflows must include the following comment at the top of the workflow file: - [ ] This workflow must only use actions that are produced by the language or ecosystem that the workflow supports. These actions must be [published to the GitHub Marketplace](https://github.com/marketplace?type=actions). We recommend that these actions be referenced using the full 40 character hash of the action's commit instead of a tag. Additionally, workflows must include the following comment at the top of the workflow file:
``` ```
# This workflow uses actions that are not certified by GitHub. # This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by # They are provided by a third-party and are governed by
# separate terms of service, privacy policy, and support # separate terms of service, privacy policy, and support
# documentation. # documentation.
``` ```
- [ ] This workflow must not send data to any 3rd party service except for the purposes of installing dependencies. - [ ] Automation and CI workflows should not send data to any 3rd party service except for the purposes of installing dependencies.
- [ ] This workflow must not use a paid service or product. - [ ] Automation and CI workflows cannot be dependent on a paid service or product.
.github/workflows/stale.yml
+20
View File
@@ -0,0 +1,20 @@
name: Mark stale issues and pull requests
on:
schedule:
- cron: "21 4 * * *"
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v3
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: 'This issue has become stale and will be closed automatically within a period of time. Sorry about that.'
stale-pr-message: 'This pull request has become stale and will be closed automatically within a period of time. Sorry about that.'
stale-issue-label: 'no-issue-activity'
stale-pr-label: 'no-pr-activity'
days-before-stale: 90
CODEOWNERS
+1
View File
@@ -0,0 +1 @@
* @actions-experience @advanced-security-code-scanning
CONTRIBUTING.md
+4 -4
View File
@@ -9,7 +9,7 @@ Contributions to this project are [released](https://help.github.com/articles/gi
Please note that this project is released with a [Contributor Code of Conduct]( Please note that this project is released with a [Contributor Code of Conduct](
https://github.com/actions/.github/blob/main/CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. https://github.com/actions/.github/blob/main/CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
**At this time we are not accepting any new starter workflows** **At this time we are only accepting new starter workflows for Code Scanning**
### Previous guidelines for new starter workflows. ### Previous guidelines for new starter workflows.
@@ -17,8 +17,8 @@ Before merging a new workflow, the following requirements need to be met:
- Should be as simple as is needed for the service. - Should be as simple as is needed for the service.
- There are many programming languages and tools out there. Right now we don't have a page that allows for a really large number of workflows, so we do have to be a little choosy about what we accept. Less popular tools or languages might not be accepted. - There are many programming languages and tools out there. Right now we don't have a page that allows for a really large number of workflows, so we do have to be a little choosy about what we accept. Less popular tools or languages might not be accepted.
- Should not send data to any 3rd party service except for the purposes of installing dependencies. - Automation and CI workflows should not send data to any 3rd party service except for the purposes of installing dependencies.
- Cannot use an Action that isn't in the `actions` organization. - Automation and CI workflows cannot be dependent on a paid service or product.
- Cannot be to a paid service or product. - We recommend that Actions outside of the `actions` organization be pinned to a specific SHA.
Thank you Thank you
LICENSE
+3 -2
View File
@@ -1,6 +1,6 @@
MIT License MIT License
Copyright (c) 2019 GitHub Copyright (c) 2020 GitHub
Permission is hereby granted, free of charge, to any person obtaining a copy Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal of this software and associated documentation files (the "Software"), to deal
@@ -18,4 +18,5 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. SOFTWARE. THIS LICENSE DOES NOT GRANT YOU RIGHTS TO USE ANY CONTRIBUTORS'
NAME, LOGO, OR TRADEMARKS.
README.md
+1
View File
@@ -13,6 +13,7 @@ These are the workflow files for helping people get started with GitHub Actions.
**Directory structure:** **Directory structure:**
* [ci](ci): solutions for Continuous Integration * [ci](ci): solutions for Continuous Integration
* [automation](automation): solutions for automating workflows. * [automation](automation): solutions for automating workflows.
* [code-scanning](code-scanning): starter workflows for [Code Scanning](https://github.com/features/security)
* [icons](icons): svg icons for the relevant template * [icons](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). 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).
automation/stale.yml
+1 -1
View File
@@ -10,7 +10,7 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/stale@v1 - uses: actions/stale@v3
with: with:
repo-token: ${{ secrets.GITHUB_TOKEN }} repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: 'Stale issue message' stale-issue-message: 'Stale issue message'
ci/blank.yml
+5 -2
View File
@@ -2,14 +2,17 @@
name: CI name: CI
# Controls when the action will run. Triggers the workflow on push or pull request # Controls when the action will run.
# events but only for the $default-branch branch
on: on:
# Triggers the workflow on push or pull request events but only for the $default-branch branch
push: push:
branches: [ $default-branch ] branches: [ $default-branch ]
pull_request: pull_request:
branches: [ $default-branch ] branches: [ $default-branch ]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# A workflow run is made up of one or more jobs that can run sequentially or in parallel # A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs: jobs:
# This workflow contains a single job called "build" # This workflow contains a single job called "build"
ci/go.yml
+2 -2
View File
@@ -30,7 +30,7 @@ jobs:
fi fi
- name: Build - name: Build
run: go build -v . run: go build -v ./...
- name: Test - name: Test
run: go test -v . run: go test -v ./...
ci/python-package.yml
+2 -2
View File
@@ -15,7 +15,7 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
strategy: strategy:
matrix: matrix:
python-version: [3.5, 3.6, 3.7, 3.8] python-version: ['3.5', '3.6', '3.7', '3.8']
steps: steps:
- uses: actions/checkout@v2 - uses: actions/checkout@v2
@@ -26,7 +26,7 @@ jobs:
- name: Install dependencies - name: Install dependencies
run: | run: |
python -m pip install --upgrade pip python -m pip install --upgrade pip
pip install flake8 pytest python -m pip install flake8 pytest
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
- name: Lint with flake8 - name: Lint with flake8
run: | run: |
script/validate-data/package-lock.json
Generated
+3 -3
View File
@@ -5,9 +5,9 @@
"requires": true, "requires": true,
"dependencies": { "dependencies": {
"@actions/core": { "@actions/core": {
"version": "1.2.4", "version": "1.2.6",
"resolved": "https://registry.npmjs.org/@actions/core/-/core-1.2.4.tgz", "resolved": "https://registry.npmjs.org/@actions/core/-/core-1.2.6.tgz",
"integrity": "sha512-YJCEq8BE3CdN8+7HPZ/4DxJjk/OkZV2FFIf+DlZTC/4iBlzYCD5yjRR6eiOS5llO11zbRltIRuKAjMKaWTE6cg==" "integrity": "sha512-ZQYitnqiyBc3D+k7LsgSBmMDVkOVidaagDG7j3fOym77jNunWRuYx7VSHa9GNfFZh+zh61xsCjRj4JxMZlDqTA=="
}, },
"@types/js-yaml": { "@types/js-yaml": {
"version": "3.12.4", "version": "3.12.4",
script/validate-data/package.json
+1 -1
View File
@@ -14,7 +14,7 @@
"typescript": "^3.9.2" "typescript": "^3.9.2"
}, },
"dependencies": { "dependencies": {
"@actions/core": "^1.2.4", "@actions/core": "^1.2.6",
"js-yaml": "^3.13.1", "js-yaml": "^3.13.1",
"jsonschema": "^1.2.6" "jsonschema": "^1.2.6"
} }