Daniel Ridge Bot issue template for updates requested needs to be improved

[ExperimentsInHonesty]

Overview

We need to update the Daniel Ridge Bot to meet quality standards when it creates a new issue. So that whenever anyone reviews the issues it's creating, we know what to do with the information being conveyed, without have to have prior knowledge of its purpose, etc.

Details

Currently, it just produces a one line status report instead of an instruction set of what to do including (action items, resources, etc.)

Action Items

• [ ] define what the bot issue should contain
  • [ ] minimum is the normal issue format
• [ ] update bot programming
• [ ] review with team
• [x] also add the role: Site Reliability Engineer automatically on creation.

Resources/Instructions

• Example of closed current state https://github.com/hackforla/ops/issues/46
• Wiki page that describes bot https://github.com/hackforla/ops/wiki/@danielridgebot-Ops-Wiki

[freaky4wrld]

@chelseybeck you put this in QA, can you tell what actually you are asking?

[ExperimentsInHonesty]

I have added this to the website dev/pm agenda for today and will get back with notes later.

• https://github.com/hackforla/website/issues/2607#issuecomment-2384632690

[roslynwythe]

• Here is a sample issue #144. Instructions are provided: ghpages-docker Wiki

[ExperimentsInHonesty]

The challenge that I see with this, is that it doesn't tell you where to make PRs to (https://github.com/hackforla/ghpages-docker) and to add the issue to the Ops and hackforla website project boards. It has instruction on how to update it but not how to fork, or how to update with a testing tag on Dockerhub, etc.