Set up Felt Chatbot development branch and prerelease workflow
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- git, github-actions, typescript
- 领域
- build-system, ci-cd, release
调研方向
Start with packages/module/release.config.js, packages/module/package.json, and the .github/workflows Check-pr.yml and release.yml files, then review the existing branch and tag setup. Done means the felt-v1 branch and prerelease stream are configured, the agreed package name and prerelease tag are set, workflows run for the branch, and CI and NPM show the expected prerelease versions.
由索引模型根据 Issue 内容生成。
描述
-
Treat Chatbot as the first Felt extension.
-
Create/configure its felt-v1 branch and prerelease stream.
-
Update package name in package.json to match the
@felt/felt-chatbotor whatever pkg name team agrees on. It should publish to NPM in this space.
“How to” docs modified from
To set up and release prereleases for extensions
- Create a new branch to be the home of your previous version:
- Branch off of your main branch with the name being the current version number
- Push that branch to your remote
- Change branches back to main
- If it doesn’t already exist: Create a git tag from the latest commit on the main branch with a name of prerelease-v${previous version number}
- i.e. prerelease-v${6}
- In the new major release branch: update
packages/module/release.config.js: - Edits to the
branchesarray: - Add a new object for your new major release branch
{ name: '<branch-name>', channel: 'prerelease', prerelease: 'prerelease' }- (optional) add a
dryRun: true - This is recommended because it helps to prevent accidentally releasing a version that you don’t mean to
- Update
./github/workflows - Edit the Check-pr.yml branches entry to include the branch name you used in step 1
- Edit the release.yml branches entry to include the branch name you used in step 1
- Check for any other workflows that fire for events on the main branch and edit the branches key as above
- Update
packages/module/package.json - Update the
publishConfigsto havetags: ‘prerelease’ - Commit and push/PR changes
- (optional) create a new branch before committing so that you can PR the changes
- Make sure to include BREAKING CHANGE: in the footer of your commit, this will let semantic-release know to increment the major version number
- Verify that everything is working properly on GitHub
- Once your PR merges / commit is pushed check the CI logs to make sure that semantic release properly detected the previous version number and increments it as you expected
- If you added dryRun: true to release.config.js in step 3 remove it in a new PR/commit
- Verify that the correct versions are appearing on NPM
Jira Issue: PF-4695
- 主要语言
- TypeScript
- 星标
- 7
- 派生
- 38
- 平均合并
- 4 天 9 小时
- 30 天内合并 PR
- 7
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
patternfly/chatbot 的其他 Issue
-
PF Team
难度 2/5 1-3 小时 新手友好度 68/100
patternfly/chatbot#919 ·
-
ChatbotWelcomePrompt: long prompt title and message overflow suggestion cards可能已有人在做 @rebeccaalpert 于 16 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
patternfly/chatbot#910 · 3 条评论 · 已指派 1 人 ·
-
PF Team
难度 2/5 1-3 小时 新手友好度 65/100
patternfly/chatbot#852 ·
-
难度 5/5 一周以上 新手友好度 42/100
patternfly/chatbot#915 ·
-
难度 3/5 1-2 天 新手友好度 64/100
patternfly/chatbot#905 · 1 条评论 ·
查看 patternfly/chatbot 的全部 Issue
相似的 Issue
-
streams:add
难度 1/5 1 小时以内 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
walletbeat/walletbeat#1558 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
hawk-digital-environments/HAWKI#438 ·
维护者通常 1 天内回复
-
Bug
难度 2/5 1-3 小时 新手友好度 72/100
GiganticMinecraft/seichi-portal-frontend#1165 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复