Try out agentic workflows for catching when product config options are deprecated
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 63
Description
This issue is an idea that we could set up GHA aw-next workflow to notice when workbench, connect, package manager repos merge changes to deprecate product config options. Could we agentically notice the change in the product repo, then file an issue or PR on this repo to update tests to react to the change.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed GHA aw-next workflow and how the workbench, connect, and package manager repositories expose product config deprecations. Define the detection, issue or PR filing, and test-update boundaries; done means the workflow reliably notices such changes and opens the intended issue or PR on this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100