Define some strategy to do functional testing for azd pipeline config
Open
area/pipeline
feature
test automation
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
Figure it out a way to prevent regressions for `azd` command `pipeline config` (other than unit test)
Make sure we can create and set up a GitHub repository, for example, and launch git actions
Contributor guide
Assessment
This issue has not been assessed yet.