chore: auto-generate README.md from toc-source.json

This commit is contained in:
github-actions[bot]
2025-07-11 02:59:58 +00:00
parent a58c8cbdfd
commit 1eec41ccbb
2 changed files with 14 additions and 3 deletions

View File

@@ -29,15 +29,21 @@ git maintenance start --schedule=hourly
#### Steps
1. Run `git maintenance start` in your repository.
2. Optionally, use `--schedule=hourly` or `--schedule=daily` to control how often maintenance runs.
3. `Git will now automatically run tasks like garbage collection, pruning unreachable objects, and optimizing internal data structures in the background`.
4. You can stop background maintenance with `git maintenance stop` if needed.
#### ProTips
> [!TIP]
> Set up maintenance on large repos to keep them fast.
> Set up maintenance on large or long-lived repos to keep them fast and healthy.
> [!TIP]
> Use with cron or scheduled tasks for automation.
> [!TIP]
> If you notice Git getting slow, check if maintenance is enabled or run it manually.
#### Links

View File

@@ -30,16 +30,21 @@ git request-pull main https://github.com/example/repo.git feature-branch
#### Steps
1. Run `git request-pull <start> <url> <end>` to generate a pull request message.
1. Identify the base commit or branch you want to compare from (e.g., main or v1.0).
2. Run `git request-pull <start> <url> <end>` to generate a pull request message.
3. Send the generated message to the project maintainer (e.g., via email or chat).
#### ProTips
> [!TIP]
> Use request-pull to generate a summary for code reviews.
> Use this command when collaborating via email or outside of web-based platforms.
> [!TIP]
> Include a clear start and end point for clarity.
> [!TIP]
> Review the generated message before sending to ensure it accurately describes your changes.
#### Links