Skip to content

docs: fix stale branch name in raw GitHub link - #59

Merged
Yangruipis merged 3 commits into
redai-studio:mainfrom
YowatariChiaki:docs/fix-wrong-branch-name-in-github-raw-link
Jul 5, 2026
Merged

Yangruipis merged 3 commits into
redai-studio:mainfrom
YowatariChiaki:docs/fix-wrong-branch-name-in-github-raw-link

Conversation

@YowatariChiaki

@YowatariChiaki YowatariChiaki commented Jul 3, 2026 •

Copy link
Copy Markdown
Contributor

What

Fix the dead links in documentation.

Why

The branch develop does not exists in GitHub.

How

Testing

  • pre-commit run --all-files passes
  • Tests pass (pytest tests/)
  • New tests added (if applicable)
  • Documentation updated (if applicable)

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • CI/CD or build changes

Screenshots / Logs

@Yangruipis

Copy link
Copy Markdown
Collaborator

Hi, thank you for your contribution – we truly appreciate your time and effort. If you have any further questions, feel free to open an issue.

@Yangruipis
Yangruipis merged commit ba81f54 into redai-studio:main Jul 5, 2026
5 checks passed
ZiyiTsang pushed a commit to ZiyiTsang/Relax that referenced this pull request Aug 6, 2026
## What

<!-- What changes does this PR introduce? -->

Fix the dead links in documentation.

## Why

<!-- Why are these changes needed? Link related issues with "Fixes redai-studio#123"
or "Relates to #456". -->

The branch `develop` does not exists in GitHub.

## How

<!-- How do the changes work? Describe the technical approach. -->

## Testing

<!-- How were the changes tested? Include commands, test results, or
screenshots. -->

- [x] `pre-commit run --all-files` passes
- [x] Tests pass (`pytest tests/`)
- [x] New tests added (if applicable)
- [x] Documentation updated (if applicable)

## Type of Change

- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] Documentation update
- [ ] Refactoring (no functional changes)
- [ ] Performance improvement
- [ ] CI/CD or build changes

## Screenshots / Logs

<!-- If applicable, add screenshots or log output to help explain the
changes. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants