Branch: refs/heads/master Home: https://github.com/openSUSE/open-build-service Commit: 1d98db6e50d1328c6abacf4b987a652231d10273 https://github.com/openSUSE/open-build-service/commit/1d98db6e50d1328c6abacf... Author: Adrian Schröter Date: 2016-04-14 (Thu, 14 Apr 2016) Changed paths: M src/api/app/controllers/webui/package_controller.rb M src/api/app/controllers/webui/patchinfo_controller.rb M src/api/app/controllers/webui/project_controller.rb M src/api/app/helpers/webui/project_helper.rb M src/api/app/models/project.rb M src/api/app/policies/project_policy.rb M src/api/app/views/webui/package/_live_log_controls.html.erb M src/api/app/views/webui/package/live_build_log.html.erb M src/api/app/views/webui/project/_packages_table.html.erb M src/api/app/views/webui/project/_tabs.html.erb M src/api/app/views/webui/project/show.html.erb Log Message: ----------- [webui] rename Project.is_remote? to defines_remote? The Project database object for remote usages is always the project defining the remote instance. find_remote delivers an additional string identifing the remote project name. We could have a is_remote? for repositories, because they can be indeed local active record objects for remote projects, but it seems we don't have the use case yet for adding this. Cleaning up some misleaded code which just crashes so far when operating on a remote project.