[#104307] Float truncate — Eustáquio Rangel <eustaquiorangel@...>
Hi!
4 messages
2021/06/16
[ruby-core:104230] [Ruby master Misc#17936] Run Travis at push on forked repository
From:
jaruga@...
Date:
2021-06-10 12:09:03 UTC
List:
ruby-core #104230
Issue #17936 has been updated by jaruga (Jun Aruga). > I sent the PR here. > https://github.com/ruby/ruby/pull/4556 The PR was merged. I expect that now you can run Travis on any branches on your forked repo without changing `.travis.yml` as well as GitHub Actions. ---------------------------------------- Misc #17936: Run Travis at push on forked repository https://bugs.ruby-lang.org/issues/17936#change-92416 * Author: jaruga (Jun Aruga) * Status: Closed * Priority: Normal ---------------------------------------- I want to change the current condition to run Travis to improve developer's experience. In my understanding, currently on ruby/ruby, Travis is executed at pull-request and push timing to only `master` or `ruby_N_N` branches by [the branches syntax part in .travis.yml](https://github.com/ruby/ruby/blob/91c542ad0570d02c269877226689085128038f54/.travis.yml#L209-L212). I think it's convenient if the developers can run Travis on their forked branches at the push timing without changing `.travis.yml`. It's like GitHub Actions. As a note, if the `branches` syntax part is removed in `.travis.yml`, it is possible to run Travis at the push timing on the forked repository even now. But it's not convenient. For example, here are the actual cases where the PR is used by developers just to check the Travis CI result. * Accept different stride sizes to heap_page_allocate: https://github.com/ruby/ruby/pull/4500 * Travis env: https://github.com/ruby/ruby/pull/4551 I am asking how to do this in the Travis community now. Maybe we need to use the `if` syntax on the top level. Conditional builds with 1 “Travis CI - Pull-Request” in pull-request and push from any branches? https://travis-ci.community/t/11673 Just removing the branches syntax part in `.travis.yml` is not enough. Because the 2 Travis builds are executed at the pull-request on the condition. You can see the picture on above Travis ticket as a reference. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>