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
We will run a full matrix CI once a day.
But for major changes for the core functionality will add a label "core functionality changes" that will trigger the full matrix CI on the specific PR in order to avoid backlash on other PR merged after the major changes merge, so we don't need to have to fix broken code later on. Major changes are something like changing to bytes for example.
For usual PR's, like commands etc, that usually has no difference between language versions, like commands and almost all PR's, will avoid triggering the whole matrix.
The text was updated successfully, but these errors were encountered:
@Yury-Fridlyand Yes it is, wasn't aware of you working on it.
If you already taking care of it, you think it'll be possible for you to add Label To the triggers of the full matrix, when the label is CoreChanges (or something similar), and to add permission protection to this trigger (so just contributors can approve and no one can misuse the label).
We will run a full matrix CI once a day.
But for major changes for the core functionality will add a label "core functionality changes" that will trigger the full matrix CI on the specific PR in order to avoid backlash on other PR merged after the major changes merge, so we don't need to have to fix broken code later on. Major changes are something like changing to bytes for example.
For usual PR's, like commands etc, that usually has no difference between language versions, like commands and almost all PR's, will avoid triggering the whole matrix.
The text was updated successfully, but these errors were encountered: