Searched full:workflow (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-latest/.github/workflows/ |
| D | stale-workflow-queue-cleanup.yml | 1 name: Stale Workflow Queue Cleanup
11 group: stale-workflow-queue-cleanup
20 - name: Delete stale queued workflow runs
21 uses: MajorScruffy/delete-old-workflow-runs@78b5af714fefaefdf74862181c467b061782719e # v0.3.0
24 # Remove any workflow runs in "queued" state for more than 1 day
|
| D | scorecards.yml | 1 # This workflow uses actions that are not certified by GitHub. They are provided
48 # https://docs.github.com/en/actions/advanced-guides/storing-workflow-data-as-artifacts
|
| D | greet_first_time_contributor.yml | 35 …s, and at [our contribution workflow](https://docs.zephyrproject.org/latest/contribute/guidelines.…
|
| D | do_not_merge.yml | 20 echo "This workflow fails so that the pull request cannot be merged."
|
| D | footprint-tracking.yml | 20 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
124 --run-workflow "footprint-tracking:${{ github.event_name }}" \
|
| D | twister-publish.yaml | 33 workflow: twister.yml
|
| D | doc-publish.yml | 29 workflow: doc-build.yml
|
| D | hello_world_multiplatform.yaml | 20 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
|
| D | doc-publish-pr.yml | 27 workflow: doc-build.yml
|
| D | bsim-tests.yaml | 32 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
|
| D | codecov.yaml | 8 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
|
| /Zephyr-latest/doc/project/ |
| D | index.rst | 23 The Zephyr project defines a development process workflow using GitHub
39 with respect to the development process workflow.
|
| D | proposals.rst | 34 The following workflow should be used to process features:.
|
| /Zephyr-latest/scripts/ |
| D | requirements-extras.txt | 1 # EXTRAS: optional or useful for development/developers workflow
|
| D | requirements-base.txt | 4 # part of the recommended workflow
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 24 * Zephyr development workflow is supported on Linux, macOS, and Windows,
|
| /Zephyr-latest/scripts/ci/ |
| D | twister_ignore.txt | 23 .github/workflows/stale-workflow-queue-cleanup.yml
|
| D | upload_test_results_es.py | 352 parser.add_argument('--run-workflow', required=False,
353 help="Source workflow identificator, e.g. the workflow short name "
|
| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 7 implemented and reviewed via the normal GitHub pull request workflow.
|
| D | guidelines.rst | 33 The Zephyr development workflow supports all 3 major operating systems
38 your Pull Request (PR). You can see any failure results in the workflow
631 Workflow subsection
644 .. _Contribution workflow:
646 Contribution Workflow argument
657 The general GitHub workflow used by Zephyr developers uses a combination of
660 workflow here:
|
| D | contributor_expectations.rst | 98 - No fixup or merge commits are allowed, see :ref:`Contribution workflow` for
203 Workflow Suggestions That Help Reviewers
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 261 Processes and workflow
266 :alt: Safety process and workflow overview
269 Safety process and workflow overview
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/ |
| D | README.rst | 17 The sample also includes a full end-to-end workflow of training
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 18 Here is an example workflow, which builds and flashes MCUboot, as well as the
|
| /Zephyr-latest/doc/develop/tools/ |
| D | clion.rst | 20 The instructions have been tested on Windows. In terms of the CLion workflow, the steps would be the
|
12
