Skip to main content

​
Document Review and Merging Process

This article will introduce the review and merging process for dance files after they are uploaded, including the creation of GitHub Issues, automatic checks, PR generation, and the final update of the dance market list.

​
GitHub Issue Creation and Review

1

Automatic Issue Creation

After the dance file upload is complete, the system will automatically create a new Issue in the lobe-vidol-market repository, containing information about the current dance file.
2

Add Labels

The newly created Issue will automatically be tagged with 💃 Dance PR.
3

Automatic Check

The system will automatically check whether the Issue content meets the parameter specifications.
4

Check Results

  • If the check passes, the Issue will be tagged with ✅ Auto Check Pass.
  • If the check fails, the 💃 Dance PR tag will be removed. You will need to modify the Issue content according to the error message, and then manually re-add the 💃 Dance PR tag to trigger a re-check.
GitHub Issue Example

​
GitHub PR Generation and Merging

1

PR Generation

After the Issue check passes, the system will automatically generate a Pull Request (PR) based on the Issue content.
2

Awaiting Review

After the PR is generated, please patiently wait for the administrator to review and merge it.
GitHub PR Example

​
Dance Market List Update

1

Automatic Build

After the PR is merged, the system will automatically run build commands to generate the updated dance list static data.
2

Market Update

LobeVidol will read the latest dance list data and display the updated content in the dance market.
Dance Market List Example