CODEOWNERS

# This is a comment.
# Each line is a file pattern followed by one or more owners.

# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @global-owner1 and @global-owner2 will be requested for
# review when someone opens a pull request.
# *       @global-owner1 @global-owner2

# Order is important; the last matching pattern takes the most
# precedence. When someone opens a pull request that only
# modifies JS files, only @js-owner and not the global
# owner(s) will be requested for a review.
# *.js    @js-owner

# You can also use email addresses if you prefer. They'll be
# used to look up users just like we do for commit author
# emails.
# *.go docs@example.com

# Teams can be specified as code owners as well. Teams should
# be identified in the format @org/team-name. Teams must have
# explicit write access to the repository. In this example,
# the octocats team in the octo-org organization owns all .txt files.
# *.txt @octo-org/octocats


/intel_extension_for_transformers/transformers/runtime/Cmake* yu.luo@intel.com
/intel_extension_for_transformers/transformers/runtime/cmake/ yu.luo@intel.com
/intel_extension_for_transformers/transformers/runtime bo1.dong@intel.com
/intel_extension_for_transformers/transformers/llm/operator bo1.dong@intel.com
/intel_extension_for_transformers/transformers/llm/evaluation chang1.wang@intel.com
/intel_extension_for_transformers/transformers/llm/finetuning liang1.lv@intel.com
/intel_extension_for_transformers/transformers/llm/inference liang1.lv@intel.com
/intel_extension_for_transformers/neural_chat liang1.lv@intel.com
/workflows/chatbot liang1.lv@intel.com
/intel_extension_for_transformers/transformers/llm/quantization penghui.cheng@intel.com
/intel_extension_for_transformers/transformers penghui.cheng@intel.com
/intel_extension_for_transformers/utils penghui.cheng@intel.com
/docs wenxin.zhang@intel.com
/.github wenxin.zhang@intel.com