- Service Overview
- Getting Started
-
User Guide
- Process of CodeArts Repo
- Environment and Personal Settings
- Accessing CodeArts Repo Homepage
- Creating and Configuring a CodeArts Project
- Configuring Project-Level Settings for CodeArts Repo
- Managing Member Permissions
- Creating a Repository
- Migrating Code and Syncing a Repository
- Configuring Repository Settings
- Configuring a Repository
- Cloning or Downloading a Repository to a Local PC
- Uploading Code Files to CodeArts Repo
- Collaborating on a Workflow
- Committing Code to CodeArts Repo and Creating a Merge Request
- Managing Merge Requests
- Managing Code Files
- Security Management
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- SSH Key
-
Repository
- Obtaining Files in a Branch Directory
- Obtaining Repository Statistics
- Obtaining Image Files of a Specific Branch in a Repository
- Modifying the Status of a Repository Referenced by a Pipeline
- Checking Whether a User Has the Repository Administrator Permission
- Setting a Repository to Public or Private
- Obtaining the Content of a Specified File in a Specified Branch of a Repository
- Obtaining a Public Template List
- Creating a Repository
- Obtaining a Repository Short ID to Generate the Details Page URL
- Querying a Commit of a Branch by Repository or Repository Group Name
- Querying Branches of a Specified Repository
- Querying a Commit of a Repository Branch by the Repository ID
- Adding a Deploy Key
- Deleting a Deploy Key
- Obtaining the Last Commit Statistics of a Repository
- Repository Statistics
- Deleting a Repository
- Viewing a Repository Creation Status
- Querying the Tag List of a Repository
- Adding a Tag
- Querying Details About a Repository
- Obtaining the number of committed code lines
- Downloading a Repository
- Creating a Protected Branch
- Deleting a Protected Branch
- Deleting Protected Branches in Batches
- Creating a Protected Tag
- Deleting a Protected Tag
- Obtaining a Repository Branch List
- Obtaining the MR List of a Repository
- Obtaining MR Details of a Repository
- Obtaining the Repository IP Address Whitelist
- Adding the Repository IP Address Whitelist
- Modifying the Repository IP Address Whitelist
- Deleting the Repository IP Address Whitelist
- Obtaining the Changes of an MR
- Associating a Repository with a Member Group
- Locking a Repository Based on the Repository Short ID
- Unlocking a Repository Based on the Repository Short ID
- Approving an MR
- Obtaining Associated Work Item Information
- Obtaining Reviewer Information Based on the Repo Short ID and Merge Request Short ID
- Obtaining the List of Changed Files
- Tenant
- Group
- Project (V2)
- RepoMember
- Commit
- File
- User
- Webhook
- Project
- Repository Management (V2)
- Review
- Application Examples
- Appendix
-
FAQs
- Authentication
- Member Permissions
-
Uploading and Downloading Code
- "Error: Deny by project hooks setting 'default': message of commit" Is Reported When Code Repository Is Pushed from the Local Host to CodeArts Repo
- Pushing Binary Files to CodeArts Repo Failed
- Error "'origin' does not appear to be a git repository..." Is Reported When the Git Push Command Is Executed
- Error "The requested URL returned error: 401" Is Reported When HTTPS Is Used to Clone Code in CentOS
- Error "Merge branch 'master' of https://test.com Please Enter a commit" Is Reported When Pulling Code Using the Git Pull Command
- Client Disconnects When a File Is Pushed
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- How Do I Prevent Files Containing Secrets from Being Pushed to CodeArts Repo?
- Migrating Repositories
- Merge Request
- Fork Sync
- Repository Capacity
- FAQs
"Error: Deny by project hooks setting 'default': message of commit" Is Reported When Code Repository Is Pushed from the Local Host to CodeArts Repo
Symptom
If the format of the code file to be pushed to the remote repository is not standard and the ticket number and modifier are not provided, the error information shown in the following figure is displayed.

Analysis
The commit message does not match the regular-expression: ^\[maven-release-plugin\]|[Trouble ticket number or requirement ticket number]\s*.+\W[Modified description]\s*.+\W[Modified reason]\s*.+\W[Modules] \s*.+\W[Modifier]\s*.+\W[Approver]\s*.+

Solution
- To modify the latest incorrect commit message, perform the following operations.
- Perform the following operations to modify the latest incorrect commit message:
Right-click the .git hidden folder and choose Open Git Bash here from the shortcut menu to open Git Bash.
- Run the git log command to find the incorrect commit message.
- Enter the information again according to the commit message specifications: ^\[maven-release-plugin\]|[Trouble ticket No. or requirement No.]\s*.+\W[Modification description]\s*.+\W[Modification reason]\s*.+\W[Module] \s*.+\W [Modified by] \s*.+\W [Approver] \s*.+. Run the git commit --amend -m'[Trouble ticket or requirement ticket ID] US20250211529 command and press Enter. Enter [Modification description] Test commit rules not qualified and press Enter. Enter [Modification reason] Test commit rules not qualified and press Enter. Enter [Module] example and press Enter. Enter [Modifier] example and press Enter. Enter [approver] Test'.
Note that there is a space between the command text and the commit message in each line.
This example indicates that the commit message set in CodeArts Repo includes the trouble ticket ID or requirement ID, modification description, modification reason, module, and modifier. Enter the information based on the your configuration settings.
- For details about how to modify the commit record that was incorrectly written for the Nth last time, see the following example (the second last).
- Run the git log command on Git Bash to search for incorrect commit messages. As shown in the following figure, there are three commit records. If the second last commit message is modified, then the ID of the second commit is e7d52124aef603f2fe94b001435962c4ffa51be9.
- Run the git rebase -i HEAD~2 command. The commit ID to be modified is e7d5212. Change pick to edit and save the modification.
- Run 3 to apply the commit message modification.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.