redhat-et / copilot-ops-bot Goto Github PK

operate-first/apps#2648 is a PR that was created by another bot
still copilot-ops bot add the created-by-copilot-ops label

operate-first/apps#2634 (comment)

see, there are 👀 on the comment

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

We want the bot code to be tested and have an upstream CI on pr/merge/release.

• probot tests (jest) - probot.github.io/docs/testing already some starting point from the template test/app.test.ts and as a unit-test it can simply validate the TaskRun payload is correctly submitted.
• tekton tests in github actions (kind) - https://garethr.dev/2019/08/running-tekton-in-a-github-action/
• pick 3 initial test cases and implement them - e.g 1) create deployment 2) create service for deployment 2) edit deployment to scale (increase replicas and resources).

On which org? redhat-et or operate-first.

probot will handle the events and submit tekton pipeline-run with these steps:

1. parse the user request from the issue description -
   • keep using the /copilot-ops way like we did here?
   • or can we tag a github app with @copilot-ops? @tumido explained this is the old way for bot user accounts.
   • labels can be used to filter out issues that are meant to our bot.
   • probot-commands - https://probot.github.io/docs/extensions/#commands
   • probot-issue-form - https://github.com/operate-first/probot-extensions/tree/main/packages/probot-issue-form
2. checkout git repo files to workspace
   • does emptyDir works across tasks in a tekton pipeline? @tumido - no, since tasks map to pods, so sharing the workspace between tasks requires a PVC, or contain everything in one task. tekton workspace still requires a volume provided to PipelineRun - see example
   • create (or use existing) branch for the issue with a fixed name - i.e. copilot-ops-issue-123
   • @tumido suggests to use one of these two examples - peribolos.../run.yaml, and this dump-config action for example dump-config.yaml#L36
   • reusing tektonhub tasks is not as simple with app authentication - https://hub.tekton.dev/tekton/task/git-clone
3. invoke copilot-ops to call the AI engine and put back the reply on the repo
   • requires redhat-et/copilot-ops#95
4. open a pr in github if not already existing using branch name copilot-ops-fixes-issue-###
   • use octokit-plugin-create-pull-request with update flag
   • what about commits added manually by the user- will update: true discard those?

Refer to previous github-actions example - https://github.com/redhat-et/copilot-ops/blob/main/.github/workflows/bot.yaml

The current readme is broken.

Provision a project on operate-first to host the bot app.
What is the release process from this repo to the deployment - perhaps a release tag or a branch.

The name used in the git commits is set to "Your Name"

Describe the solution you'd like
To prevent overload, we can add an "authorized users" list in the .copilot-ops-bot.yaml config file.

Describe alternatives you've considered
Having everybody use the bot.

Need to define how this works exactly, but the idea is that after the initial issue creation, the user can post comments (to the issue or the PR or both) and make further changes to the PR.

operate-first/apps#2633 gets 👀 but no PR 😞