1# FAQ<a name="ZH-CN_TOPIC_0000001053622377"></a> 2 3 4## Handling Simultaneous Builds for Multiple Repositories with Compilation Dependencies<a name="section169732563435"></a> 5 6During OS development, it is typical to face situations where changes in multiple repositories are interdependent for compilation, requiring concurrent builds and integrations. To manage this, the Gitee platform employs Issues as a linking identifier for PRs from multiple repositories with such dependencies. Here is how you can do it: 7 81. Create an issue in any code repository involved in your submission. 9 102. Associate PRs that 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). 11 123. Once the build is initiated (for detailed steps on triggering builds, refer to the relevant help documentation), the build center will recognize PRs linked to the same Issue. It will then download and build these PRs simultaneously and merge them into the repository after the code review is successfully passed. 13 14## Signed-off-by Operations<a name="section-signed-off"></a> 15 16### Adding a signoff Record to a Commit 17 18To include a signoff in your commit, use the command `git commit -s` or `git commit –signoff`. 19 20### Appending a signoff Record to the Most Recent Commit 21 22Simply run the command `git commit --amend --signoff`. 23 24For a comprehensive list of commit options, see [https://](https://git-scm.com/docs/git-commit)[git-scm.com/docs/git-commit](https://git-scm.com/docs/git-commit). 25 26## DCO Verification Exception Handling<a name="section-dco"></a> 27 28When you submit a PR and comments **start build**, the system triggers a gate check to verify: 29 301. Whether the PR submission includes a Developer Certificate of Origin (DCO) signature. 312. Whether the PR submission contains Signed-off-by information. 32 33If the verification fails, here are some possible reasons and solutions: 34 351. You have not signed the Developer Certificate of Origin (DCO). Example: 36 37 ``` 38 The following commits have users who have not signed the DCO agreement: 39 40 •345612 41 42 •213123 43 ``` 44 45 **Solution** 46 47 Click [here](https://dco.openharmony.cn/sign) to sign the DCO and check the signing status. 48 49 Enter **check dco** in the comment box of this PR and click **Comment**. The system will check DCO status again. 50 512. The commit does not contain Signed-off-by. Example: 52 53 ``` 54 The following commits do not contain the Signed-off-by information: 55 56 •123123 57 58 •345612 59 ``` 60 61 **Solution** 62 63 Follow the Signed-off-by instructions to add the information. The format is: Signed-off-by: user.name <user.email> 64 65 Enter **check dco** in the comment box of this PR and click **Comment**. The system will check DCO status again. 66 67 683. The email address used for the PR submission on the web/WebIDE does not match the email address used to sign the DCO agreement. 69 70 71 **Solution** 72 73 On the **Settings > Email management** page of Gitee, check whether the email address is correctly configured. Ensure that the commit email address is the same as the email address used for signing the DCO. 74 75 > **NOTE** 76 > 77 > If **Keep my email address private** is selected in **Email management**, an *xxxx@user.noreply.gitee.com* email will be used as the PR submission email by default. To use a different email for submissions, uncheck **Keep my email address private**. 78 79 80 81## Rolling Back Commits<a name="section479422315253"></a> 82 83For guidance on rolling back commits, see [https://gitee.com/help/articles/4195](https://gitee.com/help/articles/4195). 84 85## Resolving conflicts<a name="section94417232274"></a> 86 87For instructions on resolving conflicts, see [https://gitee.com/help/articles/4194](https://gitee.com/help/articles/4194). 88