The current use of Travis CI in Wikimedia repositories on GitHub does not require "installation" approval by the gh-org owners because it used hooks (Web hooks / "GitHub Services") instead of "GitHub Apps" (via "GitHub Marketplace").

The public web hooks API is not being deprecated on GitHub. Rather, the collection of built-in convenience presets are being deprecated in favour of the more flexible "GitHub Apps" integration, which in turn can also use one or more hooks (among other features, such as GitHub Checks API and others).

As part of this, Travis is also merging travis-ci.org into travis-ci.com which changes the semantics slightly, but remains effectively the same for end-users (except that it'll be easier to switch from open-source/free to private/paid plans, and to see everything together in one place).

See also:

• https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps
• https://blog.travis-ci.com/2018-05-07-announcing-support-for-github-checks-api-on-travis-ci-com
• https://docs.travis-ci.com/user/travis-migrate-to-apps-gem-guide/

I've approved the request per status quo that we already allowed its use under GitHub's previous methodology. Current repositories that were already integrated with travis-ci.org are not automatically migrated at this time, but also cannot be manually migrated. This is something that, according to Travis CiIs announcement, they will do for us at some point. Until then, they both co-exist, with any newly connected repos using the dot-com platform via GitHub Apps.