Skip to content

Latest commit

 

History

History
64 lines (49 loc) · 9.87 KB

File metadata and controls

64 lines (49 loc) · 9.87 KB

GitHub worflows

There are two workflows setup on this repo:

Worflow Status and link Description
build-test-package Build, test and package Builds the solution, runs tests and creates the NuGet packages.
upload-coverage-to-codecov Upload coverage to Codecov Uploads code coverage to Codecov.
codeql CodeQL Analyses code quality with the CodeQL tool.
dispatch-commands Slash command dispatch Handles slash commands on issues and triggers repository/workflow dispatch events.
dotnet-format dotnet format Runs dotnet format and stores the result.
dotnet-format-apply-changes dotnet format - apply changes Applies the result from the dotnet-format workflow.
markdown-link-check Markdown link check Checks markdown files for broken links and stores the result.
markdown-link-check-handle-result Markdown link check - broken links Processes the result of the markdown link check workflow.
nuget-release NuGet release Starting workflow to release a NuGet package.
nuget-publish NuGet publish Publishes NuGet packages to nuget.org and creates a GitHub release.
nuget-release-flow NuGet release flow Tracks the NuGet release flow by updating the release flow diagram and closing the release issue.
pr-dependabot-auto-merge PR Dependabot auto merge Automatically merges Dependabot PRs.
pr-test-results-comment PR test results comment Adds test results as comments on Pull Requests

Workflows' documentation

Workflow's security

All the workflows have the minimum required GITHUB_TOKEN permissions. Furthermore, the workflows that require priviliged context are separated from the ones that could potentially executed malicious code. The main purpose is to protect from the threat of malicious pull requests. For more information see:

Other relevant links:

Debugging workflows

You can print github context objects by using the toJSON function.

Example with a step running powershell:

- name: Dump github context
  shell: pwsh
  run: Write-Output '${{ toJson(github) }}'

It's useful to look at the workflow run logs, specially at the set up job section which is were you can find for example the permissions assigned to the GITHUB_TOKEN that the job will use.

You can also enable debug logging.