Skip to content
Snippets Groups Projects
Commit f3b9aab5 authored by ARUL DEVARAJAN's avatar ARUL DEVARAJAN
Browse files

Update Contribution Process.rst

parent 85db97a1
No related branches found
No related tags found
No related merge requests found
...@@ -136,4 +136,47 @@ Access the fork repository on Gitee, click the button for creating a PR, and sel ...@@ -136,4 +136,47 @@ Access the fork repository on Gitee, click the button for creating a PR, and sel
For details, visit https://gitee.com/help/articles/4128. For details, visit https://gitee.com/help/articles/4128.
.. notice::
How do I create PRs at the same time if multiple code repositories have compilation dependencies? During 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 dependency identifiers for code repositories with compilation dependencies to commit the PRs. Follow the operations below:
#. Create an issue in any of the code repositories.
#. 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.
#. 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.
Building Access Control
***********************
Creating an Issue
=================
#. Go to the homepage of the repository.
#. Click the Issues tab in the upper left corner. Then, click the issue creation button on the right, and create a dedicated task as prompted to execute continuous integration (CI) access control for associated code (feature development/bug fixing).
Associating the Issue with the PR
=================================
When creating a PR or compiling an existing PR, enter #+I+five-digit issue ID in the description box to associate the issue with the PR.
Constraints
-----------
* One PR can be associated with only one issue. Otherwise, CI cannot be triggered.
* If feature development or bug fixing involves multiple code repositories, multiple PRs can be associated with the same issue.
* Among the PRs associated with the issue, no PR that has been merged or closed is allowed. Otherwise, the CI cannot be triggered.
* If an issue has been associated with a merged or closed PR, the issue cannot be reused. In this case, create another issue and associate
it with an open PR.
Triggering Code Access Control
==============================
Comment "start build" in the PR to trigger CI access control.
If multiple PRs are associated with the same issue, the comment "start build" on any PR can trigger the CI access control of the issue.
After the access control is executed, the execution result will be automatically commented in all the PRs associated with the issue.
If the access control is passed, all PRs associated with the issue will be automatically marked as "Passed".
Reviewing Code
==============
For details, visit https://gitee.com/help/articles/4304.
Related topic: FAQs
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment