Lines Matching +full:repo +full:- +full:owner

4 [constraint_setting()](https://bazel.build/reference/be/platforms-and-toolchains#constraint_setting…
5 [constraint_value()](https://bazel.build/reference/be/platforms-and-toolchains#constraint_value)s
7 [platform()](https://bazel.build/reference/be/platforms-and-toolchains#platform)s
11 [bazel-discuss@googlegroups.com](mailto://bazel-discuss@googlegroups.com).
24 Most common constraints -- that is settings and values that can be used across
25 projects - fall into specific areas like "Apple" or "Java". These are declared
38 For the PR's reviewer(s) choose an owner of this repository plus an owner of the
43 -   semantically clear, particularly in its distinctions from other values of
46 -   well-named: consistent with existing values of the same setting and easy to
49 -   well-documented
56 New canonical constraint settings should be rare and well-justified.
60 it belongs here vs. area-specific repositories. It should clearly explain
64 are area-specific, include the area repositories' owners as reviewers.
69 fork this repo for experimental purposes. But in the interest of community
74 Note that you can declare constraint_values in your own repo that are members of
77 to use these changes - this can easily lead to fragmentation conflicts.
79 If you need custom constaint_settings, just declare them in your own repo. They
82 If you really need a permanent global change and it isn't design-approved for
83 this repo, start a thread on