feat(dev-infra): initial version of a caretaking assistant#67915
feat(dev-infra): initial version of a caretaking assistant#67915pkozlowski-opensource wants to merge 1 commit intoangular:mainfrom
Conversation
This commit introduces a skill that can act as a personal assistant for a caretaker.
angular-robot
bot
added
detected: feature
devversion
requested review from
alan-agius4 and
josephperrott
and removed request for
devversion
| A PR is considered ready for merge if it has all the reviews and required checks passing. Notably: | ||
|
|
||
| - PR has all approvals and no pending code reviews | ||
| - All required checks are passing |
There was a problem hiding this comment.
How is it to know what checks are required?
Should we note that all checks are expected to pass?
|
|
||
| - PR has all approvals and no pending code reviews | ||
| - All required checks are passing | ||
| - It merges cleanly (no merge conflicts) |
There was a problem hiding this comment.
We already determine this programmatically, we don't need an agent to do their own assessment.
There was a problem hiding this comment.
I wonder if it is worth instructing the agent to just walk through performing the merges that are available directly with the user, the agent is already running in the local environment and could be instructed to just runng-dev pr merge directly.
We currently do not have anything related to the caretaker note label. I think this is of particular interest for this type of workflow augmentation because the agent can do an assessment of the note and determine if an action can be taken.
3 participants
This commit introduces a skill that can act as a personal assistant for a caretaker.