Question: RFpeptides Branch - Should I clone the branch directly or merge with main for containerization?
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker, python
- 领域
- devops, infrastructure
调研方向
Compare the rfpeptides branch with main from their divergence at b44206a, and review the recent numbering fixes in #398. Inspect docker/Dockerfile against the branch to identify any stated container differences; done would be a maintainer-confirmed deployment recommendation covering branch selection, compatibility, and container requirements.
由索引模型根据 Issue 内容生成。
描述
Hi team!
I'm looking to build RFpeptides container and noticed that the rfpeptides branch is currently 5 commits ahead and 13 commits behind the main branch. This creates some uncertainty about the best approach for deployment.
Current situation:
- The rfpeptides branch contains RFpeptides-specific functionality not present in main
- The main branch has 13 newer commits with bug fixes and improvements (including recent chain/residue numbering fixes in #398
- Both branches have diverged since commit b44206a
My questions:
- For RFpeptides usage: Should I clone the rfpeptides branch directly, or is there a recommended way to merge it with main to get both the RFpeptides functionality AND the latest bug fixes?
- Containerization: Can I safely use the existing docker/Dockerfile with the rfpeptides branch, or are there any RFpeptides-specific container requirements?
- Branch status: Is the rfpeptides branch actively maintained? Are there plans to merge it into main or keep it as a separate feature branch?
- Compatibility: Are there any known conflicts between the RFpeptides changes and the recent improvements in main?
Any guidance on the recommended deployment strategy would be greatly appreciated!
Thanks!
- 主要语言
- Python
- 星标
- 3.1k
- 派生
- 652
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
RosettaCommons/RFdiffusion 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
RosettaCommons/RFdiffusion#456 · 3 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
RosettaCommons/RFdiffusion#453 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 20/100
RosettaCommons/RFdiffusion#449 ·
-
难度 4/5 3-5 天 新手友好度 35/100
RosettaCommons/RFdiffusion#444 · 6 条评论 ·
-
question
难度 4/5 3-5 天 新手友好度 25/100
RosettaCommons/RFdiffusion#443 ·
查看 RosettaCommons/RFdiffusion 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
WingedGuardian/GENesis-AGI#3375 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 75/100
githubnext/gh-aw-workshop#4601 ·
维护者通常 1 天内回复
-
approved Good First Issue scope: docs
难度 1/5 1 小时以内 新手友好度 85/100
hiero-ledger/hiero-sdk-python#2730 · 3 条评论 ·
维护者通常 1 天内回复