I actually think the end-state should be something like this tbh
Shit Punk Says
Oceans of Wisdom
19,517
matching drops
#1510653
2026-10-11 21:49
that now you are going to have to manually discover
and fixed them
it would for sure have discovered new things
could have done an E2E review on staging by itself
every single PR I have pushed the last 24 hours
we let them deploy to staging
the pipeline is very straightforward
i agree, we need some pipeline where agents do their own review and deploying to staging also and testing. what i also see already. doing currently 7 parallel. they are boring, i start to cut corners already etc
and they should do those before human review
and they will fix them
they will find errors
the bots are perfectly capable of running E2E tests on staging
staging is going to perform differently than the local dev environment
I think the gating factor should be deploy to production
right now the team logic at human scale is that the gating factor is "merge the code"
we are going to have lots of conflicts in a few days
does not know what branch to work on
otherwise we have a situation where anyone starting a ticket now
and then the human part should be checking the deployments before taking to production
we should let the bots go all the way to deploying and doing their own testing on staging
i am almost certain this is not the answer
random idea for starting, ai loop what can order them logically? ones what are not affecting each other and can be done parallel + then ordering confliced ones in good order
bc valued Human Team Members (tm) have to sleep, eat, etc
there is no reason to stop them working and iterating
they can do that on staging
the bots are pretty capable at E2E testing
but they go through, merge, deploy on staging, and we hold them there
which that holding point should not be at "raised a PR"
but my guess is that the stable case is to actually use staging for what it is meant for
we can discuss at the end of the day
and it is going to cause conflicts down the line
we are going to have lots of parallel branches stuck in review
which they are going to get jammed on review
but I think I know the outcome what is going to happen
I am going to give you all a couple of days
now back to the PRs
ok lets try this
we can try
it is an interesting quesiton
I guess that is something like a detailed full daily summary of what happened
and then we would make something else that is a wave
but we can think about it
i dunno if it shoudl be everyone
ofc in that case we might want to loosen up the posting rules
we have the automations but we also discussion our BOD, EOD anything that is not a sensitive topic can move here
so anything we would previously do in our dev way, can just move to here
we cover new PRs, merges and we move our dev chat here effectively
ok so I think this can be then "everything"
that is somewhere else
maybe a detailed daily summary
and then we need something else I think that is more summary