You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Homu is an implementation of the Bors merge queue bot. It's all kinds of cursed, so we want to get rid of it, and use either native GitHub merge queues (where possible) or the new bors implementation in the rest of the repos (mainly https://github.com/rust-lang/rust).
Getting rid of homu could allow us to also get rid of the rust-lang-ci organization and just run all CI under the rust-lang org and it would also help with getting rust-lang/rust managed under team (rust-lang/team#1463).
Below is a list of things that we need to resolve to reach that goal (in more or less the required order):
Reduce the amount of repositories that use homu, even though they do not have to.
(optional) Make it possible to configure GitHub merge queues in team. Sadly, it is not possible to do using the current API, because GitHub refuses to support it. We would probably need to switch from branch protections to merge rules. This is not a big issue though, only a few repositories use merge queues, and infra-admins can configure these manually, as it's a one-time action (more or less, see the linked document below).
Make it possible to configure homu/bors per branch protection, not just per repository. This would allos us to specify more precisely which branches are managed by homu, and also to use both homu and the new bors on the same repository.
Implement support for the new bors into team and sync-team. Allow specifying e.g. bors2 in the bots array, and implement installation of the bors GitHub app in sync-team.
Configure CI permissions/secrets for the new bors. To avoid Partial credentials found in env, missing: AWS_SECRET_ACCESS_KEY.
Manually configure access to main, stable, beta, automation/bors/auto and automation/bors/auto-merge branches for the production bors GitHub app (has to be done by an infra admin)
Homu is an implementation of the Bors merge queue bot. It's all kinds of cursed, so we want to get rid of it, and use either native GitHub merge queues (where possible) or the new bors implementation in the rest of the repos (mainly https://github.com/rust-lang/rust).
Getting rid of
homucould allow us to also get rid of therust-lang-ciorganization and just run all CI under therust-langorg and it would also help with gettingrust-lang/rustmanaged underteam(rust-lang/team#1463).Below is a list of things that we need to resolve to reach that goal (in more or less the required order):
merge-botsconfiguration per branch protection team#1576teamandsync-team. Allow specifying e.g.bors2in thebotsarray, and implement installation of the bors GitHub app insync-team.Partial credentials found in env, missing: AWS_SECRET_ACCESS_KEY.@bors tryto new bors, or add a hint to homu that people can do@bors2 tryinstead.rust-langinstead ofrust-lang-citeam(Add bors merge bot team#2202)rust-lang/rustinteam(Configure bors for rust-lang/rust team#2203)main,stable,beta,automation/bors/autoandautomation/bors/auto-mergebranches for the production bors GitHub app (has to be done by an infra admin)rust-lang/rust(Update bors configuration rust#150308)@bors2prefix bors#550)@bors2to@bors(Use@borsprefix for new bors simpleinfra#869)rust-lang/rust(Enable merge queue in new bors rust#150708)bors build finishedjob topublish toolstaterust#150772)autoandtrybranches and their branch protections (Remove legacy homutryandautobranch mentions rust#150771, Removetry/autohomu branch protections fromrust-lang/rustteam#2216)Fix promote-release usage of homu e-mailProbably doesn't need a fix.homuteam#2217)