[英]Github structuring for release cycles
I'm reasonably new to using Github and I don't think I'm trying to do the simplest thing so I could really do with some help. 我是使用Github的新手,我认为我没有尝试做最简单的事情,因此我确实可以提供一些帮助。 I think I'm almost there.
我想我快到了。
Here's what I'm trying to achieve. 这就是我想要实现的目标。
Here's how my Node Express server receives the webhook: 这是我的Node Express服务器接收Webhook的方式:
app.post("/", function(req, res){
//event is not a release
if (req.headers["x-github-event"] != "release") return;
//push release to test or live server
else if (req.body.release.prerelease) pushToDev(req);
else if (!req.body.release.prerelease) pushToLive(req);
});
Everything for doing a prerelease is working fine. 进行预发行的一切工作正常。 I'm just not sure about a couple of things:
我只是不确定以下几点:
Yes, you should consider using branches - this is a common scenario, and there are some good solutions for this. 是的,您应该考虑使用分支-这是常见的情况,为此有一些好的解决方案。
Atlassian has a pretty good overview of possible workflows here, comparing different branching workflows . Atlassian 在这里对可能的工作流程进行了很好的概述,比较了不同的分支工作流程 。
A popular workflow is Git-Flow , also described here . 流行的工作流程是Git-Flow ,也在此处介绍。
With Git-Flow, you work on a develop
branch and feature branches to do your work. 使用Git-Flow,您可以在
develop
分支和功能分支上工作。 All of your releases are done from release branches and then merged into the master
branch. 您的所有发行都是从发行分支完成的,然后合并到
master
分支中。
So in your case, your prerelease could be done in a release branch (or even in master), while you continue to work in develop
to make additional changes. 因此,在您的情况下,可以在发行分支(甚至在母版中)进行预发行,同时继续进行
develop
以进行其他更改。 Once the prerelease has been tested, you can create a real release from that branch. 一旦测试了预发行版,就可以从该分支创建真实的发行版。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.