CI: Have the CI create a draft release on tag#20
Conversation
If you tag and push it to the TheList repository, a draft release will be generated that only the respository owner can see. They then have the opportunity to test, amend and maybe publish it. Note that the tag name will be used in someplaces such as the assert name for the zipfile / notes.
|
Is it not possible to GitHub's CI/CD do that when it receives a commit or merge? Although they are both Git, I know they are different. But over at the FreeDOS Archive on GitLab, I used to have the CI/CD do that and automatically push a release. The problem with that was there are so many projects under the one namespace. It was eating into the 10Gb limit on the Free Tier quite a lot. It was also hitting the CI/CD time limit. Pruning old release files across all of those projects was a nightmare. So, I ended up turning off the CI/CD runners, deleting all those builds and removing the CI/CD configuration stuff from all of those projects. But, it was doable over there. I don't know about here. Even if that cannot be done here, it is not worth moving it because of the limit headaches and a few other reasons. |
|
I think so, I just couldn't imagine you'd want that many releases. Will check tomorrow. |
|
@andrewbird well, what I was hoping for was something like a nightly build type of release. Just one release which is always up to date. Then have a “version release” at much longer intervals. but, what I am thinking now is just to have my server fetch and build one. It would likely be the easiest and most reliable way to have one. Then provide a link or something from here to fetch that build from my server. So, you don’t need to worry about trying to force GitHub into doing it. |
That's probably nicer than pushing from here to your server as you won't have to deal with authentication, you can just git pull the public repo on a poll and build if something changes. |
2 participants
If you tag and push to the TheList repository, a draft release will be generated that only the repository owner can see. They then have the opportunity to test, amend and maybe publish it.
Note that the tag name will be used in some places such as the assert name for the zip file / notes.
See https://github.com/andrewbird/thelist/releases as an example of what the draft might look like after I mostly accepted the defaults (except adding the prerelease tag)