-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
可以在企业微信里面发通知吗? #8
Comments
感谢关注,目前还不支持企业微信,我先去调研一下,能支持的话,尽快同步给你哦(๑˙ー˙๑) |
你好, 安装 v1.3.0 最新版就可以发送部署消息到企业微信了, 具体使用方法请参考文档 支持推送部署成功的通知到 企业微信(WeCom) 群聊 感谢反馈, 如有其他疑问欢迎提 issue 给我❤️ |
请教一下哈,这部分写入到哪个文件里面?
…------------------ 原始邮件 ------------------
发件人: "guMcrey/version-rocket" ***@***.***>;
发送时间: 2022年8月21日(星期天) 下午4:53
***@***.***>;
***@***.******@***.***>;
主题: Re: [guMcrey/version-rocket] 可以在企业微信里面发通知吗? (Issue #8)
你好, 安装 v1.3.0 最新版就可以发送部署消息到企业微信了, 具体使用方法请参考文档 支持推送部署成功的通知到 企业微信(WeCom) 群聊
感谢反馈, 如有其他疑问欢迎提 issue 给我❤️
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@HelloWorldya
{
// 消息卡片标题
"title": "TEST FE Deployed Successfully",
// 可选: 项目名称标签, 默认 Project Name
"projectNameLabel": "Project name label",
// 项目名称
"projectName": "TEST",
// 可选: 项目分支标签, 默认 Branch
"branchLabel": "Branch label",
// 项目分支, 可用于区别部署环境
"branch": "Staging",
// 可选: 版本标签, 默认 Version
"versionLabel": "Version label",
// 版本
"version": "1.1.1.0",
// 可选: 项目可访问地址标签, 默认 URL
"accessUrlLabel": "Access URL label",
// 项目可访问地址
"accessUrl": "https://test.com",
// 是否@所有人: true / false
"isNotifyAll": true,
// 企业微信机器人的 webhook 链接
"webHook": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxxxxxxxxxxx",
// 可选: 部署工具描述
"deployToolsText": "Deploy tools text",
// 可选: 部署时间想要转换成的时区,默认 "Asia/Shanghai" (当你的项目要部署的目标服务器与你所在时区不同, 可以设置此字段来转换时区)
"expectConvertToTimezone": "America/New_York"
// 可选: 想要展示除模版之外的更多信息
"remark": "Trigger by bob, fix xxx bug"
}
// package.json
{
"name": "test",
...
"scripts":
"send-wecom-message:test": "send-wecom-message"
...
},
...
}
更多详情参见文档,感谢关注 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: