Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Anyone attempted to make a devops pipeline with Github Actions and TabCmd?

未关闭
#311 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
github-actions, python
领域
ci-cd, cli, devops

调研方向

No repository files, tests, or entry points are named. Start by determining how tabcmd can be invoked from GitHub Actions; done would be a documented, working approach for publishing to test and production, handling extract scheduling, and keeping extracts out of the repository.

由索引模型根据 Issue 内容生成。

描述

I can only find very old examples of people attempting this online. I'm wondering if anyone that is active in Tabcmd project has done this before and could provide any examples. Here is my goal:

  1. We have two separate on-premise servers - tabsrv_test and tabsrv_prd
  2. I'd like to have a github repo with two branches: test and prd. These two branches would exactly mimic the folder structure in tableau.
  3. When a new tableau workbook is published to test branch, github actions uses tabcmd to publish the workbook. The same would occur when merged to master.

What I'm unsure about:

  1. Is this even possible
  2. How do you handle scheduling of extracts - separate yaml configuration file and tabcmd?
  3. seems like a bad idea for tableau extracts to host in github. Is there a way to work around this and use yaml configuration to handle it? Any recommendations?

Any advice or knowledge sharing here would be great. I'd be happy to share back if I get this working.

主要语言
Python
星标
52
派生
17
平均合并
5 天 20 小时
30 天内合并 PR
2

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tableau/tabcmd 的其他 Issue

查看 tableau/tabcmd 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。