Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of CodeArts Repo
- Purchasing CodeArts
- Accessing CodeArts Repo Homepage
- Environment and Personal Settings
- Migrating Code and Syncing a Repository
- Creating a Repository
- Viewing Activities
- Viewing Repository Statistics
- Configuring Repository Settings
- Hierarchical Repository Management
- Configuring a Repository
- Managing Repo Member Permissions
- Cloning or Downloading Code Repo to a Local PC
- Uploading Code Files to CodeArts Repo
- Developing a Workflow
- Creating and Configuring a CodeArts Project
- Committing Code to CodeArts Repo and Creating a Merge Request
- Managing Merge Requests
- Managing Code Files
- Security Management
- Best Practices
-
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
- 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
-
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
- Videos
- General Reference
Copied.
Viewing Commit History
CodeArts Repo allows you to view details about the commit history and related file changes. You can view the commit history on the Activities tab page of a repo or on the History tab page of a repo file list.
Viewing the Commit History on the Repo Activities Page
Go to the homepage of the code repository to be viewed and click Activities to view all activities of the repositories. To view the activities within a specified period, select a period on the right. To view the activities of a repo member, select the repo member from the drop-down list box on the right.
- All: If no time range or member is selected, the operation records of all members in the repo are displayed.
- Push: If no time range or member is selected, the push records of all members in the repository are displayed, for example, code push, branch creation, and branch deletion.
- Merge Request: If no time range or member is selected, the merge request records of all members in the repository are displayed. You can click the sequence number of a merge request to view details, such as creating, closing, re-opening, and merging MRs.
- Review: This tab displays all review comments of the repository. You can click the commit ID to view details such as adding or deleting comments.
- Member: This tab displays the management records of all members in the repository, for example, adding or removing members and editing member permissions.
- The displayed information includes the operator, operation content, and operation time.
- You can specify search criteria, such as the time range and operator, to filter and query data.
You can view the commit history on the History tab page of the Files or Activities tab. You can click a commit record to view the committer, commit number, parent node, number of comments, and code change comparisons.
You can comment on a commit or reply to a comment.
You can click the icon in the following figure to switch the horizontal or vertical display of code change comparison. You can click Show All to view the full text of the files involved in the commit.
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