Configuring Push Permissions
Constraints
Item |
Description |
---|---|
Permission constraint |
To configure push permission rules for a repository, you must have the set permission on the repository. For details, see Configuring Repo-Level Permissions. |
Configuring Push Permissions for Code Files
- Go to the homepage of the repository Test_JAVA_Demo, choose Settings > Policy Settings > Push Permissions, and click Create Push Policy.
- Set parameters based on Table 2. As shown in the following figure, Test/* indicates that only Developer can push all files in the Test/ directory.
Parameter |
Description |
---|---|
File Path |
Enter a complete path or a path with a wildcard as required. Only one path can be added at a time. Batch addition is not supported. The path can contain a maximum of 256 characters. |
Add Permissions |
Optional. It indicates the roles allowed to push files. You can select member groups, members, or roles from the drop-down list. If you do not add any member group, member, or role, no one can push files in this path or files that comply with the wildcard path rule. |
Managing Push Permission Rules
Click in the row where the push permission rule is located to modify roles with this permission.
Click in the Operation column of the push permission rule to delete it.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot