Sharp Stock

English

简体中文

English

简体中文

Resource Sync & Version Commit (SVN) ​

This chapter provides a detailed introduction to the specific operation procedures and core precautions for version synchronization in Sharp Stock.

1. Resource Update Operation (Update) ​

When the "Update" button at the bottom of the navigation bar is green, it indicates pending updates on the server.

Update Feedback ​

  • Execution Process: After clicking the button, the system enters an automated synchronization phase; please wait patiently for the task to complete.
  • Subsequent Processing: Once synchronization is finished, the software automatically re-scans affected directories and refreshes thumbnails, asset lists, and metadata, ensuring the local state is fully aligned with the server.

Operation Recommendation ​

  • Sync First: Before starting large-scale modifications to resources, develop a habit of executing an "Update" first to ensure you are creating based on the latest version, effectively avoiding conflicts.

2. Asset Commit Operation (Commit) ​

Clicking the "Commit" button will call up the version upload confirmation dialog.

Core Item Description ​

  • Pending Commit List: Clearly lists all physical paths intended for upload and marks the status of each asset (e.g., added, modified, deleted).
  • Change Description (Required): Please briefly summarize the core content of this commit. Good commenting habits significantly improve the team's later traceability and collaboration efficiency.
  • Confirm Commit: After verifying, click "Confirm"; the upload task will be executed in the background. Once complete, the commit button will return to its regular grey state.

SVN Commit Dialog Operation Interface

3. Common Execution Result Handling ​

  • Commit Successful: The system will pop up a success prompt, and the sidebar sync buttons will refresh accordingly.
  • Pre-Update Reminder: If the server version is already ahead of local, the system will block the commit and prompt you to perform an [Update] first.
  • Account Permission Anomaly: If an authentication failure is prompted, it may be due to an expired SVN password or changed permissions; you need to re-log in and authorize via professional SVN tools in the local directory.

4. Metadata Synchronization Strategy ​

Tags and notes are committed synchronously. When you label assets with tags or notes, this metadata is included as part of the library database and uploaded along with the files when you execute a commit. Team members will be able to see all your management information locally after updating resources.

5. Safety Collaboration Suggestions ​

  • Structural Change Tip: If large-scale directory moves or renames are involved, we recommend verifying physical path accuracy via a professional SVN client before performing a unified commit within the app.
  • Conflict Avoidance: If the system prompts a Version Conflict, please prioritize referring to the Conflict Resolution chapter; never attempt to force repeat commits without resolving the conflict.