docs: update repository links to forumlify/public - #27
Conversation
|
Automated review has started. I am checking this pull request now. |
Bundle ReportBundle size has no change ✅ Affected Assets, Files, and Routes:view changes for bundle: forumlify-next-client-array-pushAssets Changed:
|
|
Automated review completed for commit |
![forumlify[bot]](https://avatars.githubusercontent.com/in/4581425?s=60&v=4){kind=small}
There was a problem hiding this comment.
Superseded automated review
The review for commit 59edccac4582 has been replaced by the automated review for commit 6202d89e264f.
Its previous inline review and change comments were removed. Refer to the latest commit review for the current result.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
/recheck |
|
Automated review completed for commit |
|
Recheck requested by @lezi-fun. Re-running the review with the repository's current strictness settings. |
There was a problem hiding this comment.
Superseded automated review
The review for commit 6202d89e264f has been replaced by the automated review for commit 6202d89e264f.
Its previous inline review and change comments were removed. Refer to the latest commit review for the current result.
Superseded by the automated review for commit 6202d89.
There was a problem hiding this comment.
Automated review
Mode: normal
Comment
The migration from furrium/forumlify to forumlify/public is now consistent throughout: both git clone blocks use the new URL and correctly cd public (the directory name git derives from the repo name), and the docker pull / docker-compose.yml image reference both point to ghcr.io/forumlify/public:next. The previous blocking issue where README still said cd forumlify has been fixed in both the Docker quick start and the source-build sections. No remaining issues found.
Result for maintainers
The PR consistently updates all repository references to the new forumlify/public location: README clone URLs now match the resulting local directory (cd public in both Docker quick start and source-build sections), and the GHCR image references in README and docker-compose.yml both use ghcr.io/forumlify/public:next, which is consistent with GHCR naming derived from the repository. No correctness, security, build, or runtime issues found.
Model decision: safe to merge
Applied review policy: allow
Final status: safe to merge
Required changes: 0
Review notes: 0
Superseded by the automated review for commit 6202d89.
|
@bot Introduce it |
1 similar comment
|
@bot Introduce it |
|
这是一次纯文档/配置的仓库迁移跟进 PR，介绍如下： 这个 PR 做了什么Forumlify 仓库已从 改动共 4 处，涉及 2 个文件：
为什么这样改
一个小提示PR 描述中提到共 3 处 README 改动，加上 docker-compose.yml 实际是 4 处替换。建议合并前顺手确认一下仓库里（如 CI workflow、 |
|
@bot Who am I in relation to this PR, and can you summarize it in one sentence? |
|
You are the author of this PR and a repository admin ( In one sentence: This PR updates all repository references from the old |
1 participant
目标分支 / Target branch
变更内容 / What does this PR do?
将 README 中所有旧仓库地址
furrium/forumlify更新为新的 org 仓库地址forumlify/public（仓库已迁移至 forumlify org）。/ Update all old repository references from
furrium/forumlifyto the new org repoforumlify/public(the repository has moved to the forumlify org).共 3 处 / 3 places:
git clone地址 /git cloneURL in Docker quick startdocker pull ghcr.io/forumlify/public:next（镜像名由 workflow 的${{ github.repository }}动态生成，随仓库迁移自动变更）/docker pull ghcr.io/forumlify/public:next(image name is generated from${{ github.repository }}in the workflow, so it follows the repo move)git clone地址 /git cloneURL in source build section测试 / Testing
furrium/forumlify引用 / Verified no remainingfurrium/forumlifyreferences in README检查清单 / Checklist