1# FAQs<a name="EN-US_TOPIC_0000001053622377"></a> 2 3[How Do I Create PRs at the Same Time If Multiple Code Repositories Have Compilation Dependencies?](#section169732563435) 4 5[Sign-off-by Operations](#section-sign-off) 6 7[Handling Exceptions of DCO Verification](#section-dco) 8 9[Rollback](#section479422315253) 10 11[Resolving Merge Conflicts](#section94417232274) 12 13## How Do I Create PRs at the Same Time If Multiple Code Repositories Have Compilation Dependencies?<a name="section169732563435"></a> 14 15During the development of the operating system \(OS\), it is common that multiple code repositories have compilation dependencies. Therefore, the PRs need to be created and merged at the same time. For this reason, Gitee uses issues as the association identifiers for code repositories with dependency dependencies to commit the PRs. Follow the operations below: 16 171. Create an issue in any of the code repositories. 182. Associate PRs need to be built and merged at the same time with the issue. For details, visit [https://gitee.com/help/articles/4142](https://gitee.com/help/articles/4142). 193. After the build is triggered, the build center identifies the PRs associated with the same issue, downloads the build, and merges the PRs into the code library after the code is approved. 20 21## Sign-off-by Operations<a name="section-sign-off"></a> 22 23#### How to Add signoff Records in Commits? 24 25Execute the **git commit -s **or **git commit –signo** command to submit signoff records. 26 27#### How to Add a signoff record to the Previous Commit? 28 29Execute the **git commit --amend --signoff** command. 30 31For more options about commit, see [https://](https://git-scm.com/docs/git-commit)[git-scm.com/docs/git-commit](https://git-scm.com/docs/git-commit). 32 33## Handling Exceptions of DCO Verification<a name="section-dco"></a> 34 35After developers submit Pull Request, commenting "**start build**" in the PR will trigger the gated commit. In this sense, you should consider: 36 371. Whether the DCO is signed. 382. Whether the commits contain Signed-off-by information. 39 40The possible causes for a verification failure include: 41 421. The DCO is not signed. The following messages will be displayed: 43 44 ``` 45 The following commit users do not signed the DCO: 46 47 •345612 48 49 •213123 50 ``` 51 52 **Solution** 53 54 Click [https://dco.openharmony.io/sign/Z2l0ZWUlMkZvcGVuX2hhcm1vbnk=) to sign the DCO or check the signing status. 55 56 Enter **check dco** in the Pull Requests comment box and click **Comment**. The system will check the DCO signing status again. 57 582. The commits do not contain Signed-off-by information. The following messages will be displayed: 59 60 ``` 61 The following commits do not contain Sign-off-by information: 62 63 •345612 64 65 •213123 66 ``` 67 68 **Solution** 69 70 Add the Sign-off-by information by referring to **Sign-off-by Operations**. 71 72 Enter **check dco** in the Pull Requests comment box and click **Comment**. The system will check the DCO signing status again. 73 74## Rollback<a name="section479422315253"></a> 75 76Visit [https://gitee.com/help/articles/4195](https://gitee.com/help/articles/4195). 77 78## Resolving Merge Conflicts<a name="section94417232274"></a> 79 80Visit [https://gitee.com/help/articles/4194](https://gitee.com/help/articles/4194). 81 82