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
No so long time ago we faced with the problem of updating .rultor.yml. The problem is that we can not update .rultor.yml by using default development approach - through PR`s:
this particular commit rultor wouldn't catch, because it uses .rultor.yml from master. I don't push to master, but this one was the only possible option
No so long time ago we faced with the problem of updating
.rultor.yml
. The problem is that we can not update.rultor.yml
by using default development approach - through PR`s:objectionary/eo#1949 (comment)
This is quite risky: even rare direct pushes to a default branch can break all CI pipelines and break development process.
I'm aware about that problem, but since it doesn't explain possible threats, I don't see vulnerabilities in that approach.
The text was updated successfully, but these errors were encountered: