dapr/dapr

Proposal: Use workflow_dispatch for dapr-bot commands

Open

#5,526 opened on Nov 16, 2022

View on GitHubContributor guide
 (1 comment) (1 reaction) (1 assignee)Go (2,064 forks)batch import
P2good first issuepinned

Repository metrics

Stars
 (25,672 stars)
PR merge metrics
 (Avg merge 2d 19h) (63 merged PRs in 30d)

Description

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the proposal

Currently, the dapr_bot is using the repository_dispatch event - which can only trigger workflows based on default-branch workflow yaml, for running commands like /ok-to-perf and /ok-to-test.

See this as an example, the dapr-perf.yaml file being used is from master branch (which is the default one).

This proposal aims to change the event trigger to use the workflow_dispatch event so that we can verify and validate branch modifications for workflows before those being merged into the master branch.

Contributor guide

Research direction
Investigate the current usage of repository dispatch in dapr workflow files (e.g., dapr perf.yaml). Understand the differences between repository dispatch and workflow dispatch. Identify which workflows use dapr bot commands and need trigger changes. Propose switching to workflow dispatch with appropriate inputs.
Tech stack
github actions
Domain
devopsci cdrelease
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub ActionsYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70