1# FAQs 2 3## How Do I Create PRs at the Same Time If Multiple Code Repositories Have Compilation Dependencies? 4 5During 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: 6 71. Create an issue in any of the code repositories. 82. 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). 93. 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. 10 11## Sign-off-by Operations 12 13#### How to Add signoff Records in Commits? 14 15Execute the **git commit -s **or **git commit –sigoff** command to submit signoff records. 16 17#### How to Add a signoff record to the Previous Commit? 18 19Execute the **git commit --amend --signoff** command. 20 21For 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). 22 23## Handling Exceptions of DCO Verification 24 25After developers submit Pull Request, commenting "**start build**" in the PR will trigger the gated commit. In this sense, you should consider: 26 271. Whether the DCO is signed. 282. Whether the commits contain Signed-off-by information. 29 30The possible causes for a verification failure include: 31 321. The DCO is not signed. The following messages will be displayed: 33 34 ``` 35 The following commit users do not signed the DCO: 36 37 •345612 38 39 •213123 40 ``` 41 42 **Solution** 43 44 Click [here](https://dco.openharmony.cn/sign) to sign the DCO or check the signing status. 45 46 Enter **check dco** in the Pull Requests comment box and click **Comment**. The system will check the DCO signing status again. 47 482. The commits do not contain Signed-off-by information. The following messages will be displayed: 49 50 ``` 51 The following commits do not contain Sign-off-by information: 52 53 •345612 54 55 •213123 56 ``` 57 58 **Solution** 59 60 Add the Sign-off-by information by referring to **Sign-off-by Operations**. 61 62 Enter **check dco** in the Pull Requests comment box and click **Comment**. The system will check the DCO signing status again. 63 64## Rollback 65 66Visit [https://gitee.com/help/articles/4195](https://gitee.com/help/articles/4195). 67 68## Resolving Merge Conflicts 69 70Visit [https://gitee.com/help/articles/4194](https://gitee.com/help/articles/4194). 71 72