ford prior

UPDATE: I ended up deleting the `epic.yaml` and `task.yaml` because we seldom use these templates. Instead, we'll rely on the `story.yaml` for internal stories and `bug.yaml`/`enhancement.yaml` for external requests.

This is a close relative to https://github.com/awsdocs/aws-doc-sdk-examples/issues/3295. Not duplicate. @ford-at-aws will do the following: * ask team for anecdotes about issue template problems (for [all 7 issues)](https://github.com/awsdocs/aws-doc-sdk-examples/issues/new/choose) * collect data...

Close relative of https://github.com/awsdocs/aws-doc-sdk-examples/issues/3295. Not duplicate. @meyertst-aws will do the following: 1. ask team for anecdotes about issue template problems 2. collect data on current issue (e.g. created by whom?)...

Any update on this issue?

👋 From AWS! We rely on this labeling solution and would love to see this bug worked out. Thanks!

# Research findings for Ruby clean-up The following is the work I've identified in my research to be high priority for Ruby clean-up effort. I will organize the work units...

https://gist.github.com/ford-at-aws/39ff3fe9929152cb7614b6df1729dbb1

- [ ] workdocs (1 broken test) - [x] lambda (4) - [x] elastictranscoder (3) - [x] cloudtrail (1) - [x] s3 (1)

Possible language: ``` To view the results of our linting configurations on your own fork, click the Actions tab and Alternatively, you can install the package locally and execute the...

Don't forget: 1. Jason feedback 2. Brian feedback