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
{{ message }}
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.
I was wondering if we could put all the regression testing against new kernel into the separate pull request
or into the separate branch?
Here is my vision how it can be actually implemented:
$ git checkout master-travis
$ git reset --hard master
$ <do_update .travis.yml>
$ git commit -a --no-edit
$ git diff master master-travis --exit-code || git push --force
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was wondering if we could put all the regression testing against new kernel into the separate pull request
or into the separate branch?
Here is my vision how it can be actually implemented:
$ git checkout master-travis
$ git reset --hard master
$ <do_update .travis.yml>
$ git commit -a --no-edit
$ git diff master master-travis --exit-code || git push --force
The text was updated successfully, but these errors were encountered: