IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
if you want to contest this change, please do go ahead and let us know
you'd benefit from having these enabled. originally they were added
because adding multiple images to build worked most of the time without
any downside with unlimited free CI.
437: ci: no longer require review approvals to merge r=koivunej a=koivunej
This PR will allow `bors r+` before there are any review approvals. It will be good for smaller PRs like #436 or things which happen right before releasing. Alternatives include:
- to request and await for approvals (current situation)
- to merge without bors -- this is something I'd like to avoid doing
Now bors uses the PRs configuration so I don't require any approvals on this, but it has to come after #436 so that the workflow is fixed so at least this is gated on that :) So @aphelionz, @ljedrz, or anyone interested in this, how do you see this? I think the policy should still be to review all non-boring maintenance PRs.
I did check CONTRIBUTING.md and found that there is nothing regarding this.
I'll merge this at the earliest of tomorrow morning on +02:00.
Co-authored-by: Joonas Koivunen <joonas.koivunen@gmail.com>
bors behaviour changed some time ago w.r.t. having tasks with a single
name but one passed and one skipped. perhaps this will work without one
as well.
the warning is quite unuseful since we haven't had a single core dump
after adding it, however there are important warnings from workflows we
should pay attention to.
also, adding a platform limitation cant be done because the ${{ always()
}} seems to have the highest priority.
the cross builders might end up otherwise poisoning the cache with an
empty npm. this may have already happened and explains why it didn't
work for mac and linux.
also include the patches again in the cache key.
