跳到主要内容

Pre-release Status

To ensure the high quality of models and datasets on the platform, GitCode implements a document review mechanism to check resources submitted by users. If any of the following situations are found during the review, the model or dataset will be set to pre-release status:

Rules for Pre-release Status​

Model Library​

If your model library meets any of the following conditions, it will enter pre-release status:

  1. Insufficient README Content: The number of words in the README file is less than 200 or uses the platform's default template.
  2. Insufficient File Types: No files other than .gitattributes, README.md, config.json, or configuration.json have been uploaded.
  3. Non-standard Name: The project name is only "test" or "测试".
  4. Missing LFS Files: LFS files are not uploaded in the project, or the file import is not yet complete.

Dataset​

If a dataset has any of the following issues, it will also be marked as pre-release status:

  1. Non-standard Name: The dataset name is only "test" or "测试".
  2. Insufficient File Types: The dataset contains only the following files:
    • README.md
    • dataset_infos.json
    • A JSON file with the same name as the dataset, or an empty Python file (if the Python file is not empty, this rule does not apply).

Impact of Pre-release Status​

Models or datasets in pre-release status will be set as private resources and cannot be displayed on the list page or found through search functionality. We hope developers actively improve their resources and ensure their quality. We welcome your participation in building a better community with GitCode.

How to Appeal Pre-release Status​

If you have any questions about the model or dataset being set to pre-release status, please contact customer service online or call 400-6868-951 promptly. When appealing, please provide the following information:

  • Model/Dataset Name: Specify the name of the resource set to pre-release status (in Chinese or English).
  • Provider Information: If the resource was created by an individual, provide the username; if created by an organization, fill in the organization name.
  • Remarks: Provide detailed reasons why you believe the resource should not be marked as pre-release status and include any additional relevant information.

GitCode encourages developers to actively share resources and is committed to improving the quality of models and datasets together with community members. Thank you for your understanding and support!