pubkey, twofa, basesigned, commitssigned: [never, pubkey, twofa, approved, basesigned, commitssigned, always]: 对合并操作进行签名。 approved : 仅对已批准的合并操作进行签名，适用于受保护的分支。 basesigned : 仅在基础仓库的父提交进行了签名时才进行签名。 SHARE_USER_STATISTICS ：true：如果启用联邦，则启用/禁用节点信息的用户统计信息。 MAX_SIZE ：4：联邦请求和响应的最大大小（MB）。 警告：更改以下设置可能会破坏联邦功能。 ALGORITHMS ：rsa-sha256, rsa-sha512, ed25519：HTTP 签名算法。 DIGEST_ALGORITHM ：SHA-256：HTTP 签名摘要算法。 GET_HEADERS ：仅在基础仓库中的父提交已签名时进行签名。 headsigned ：仅在头分支中的头提交已签名时进行签名。 commitssigned ：仅在头分支中的所有提交到合并点的提交都已签名时进行签名。 approved ：仅对已批准的合并到受保护分支的提交进行签名。 always ：始终签名 除了 never 和 always 之外的选项可以组合为逗号分隔的列表。如果所有选择的选项都为 true，则合并将被

broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit

broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit your

broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit your