Tagging releases #6833
Replies: 2 comments
-
@jessevanmuijden - This looks really good. My humble recommendation would be create something simple, functional and beta. Namely, a beta feature people can opt into that isn't necessarily feature complete but that provides a first step in functionality toward bundling together a number of content changes into one build. |
Beta Was this translation helpful? Give feedback.
-
@jessevanmuijden - Just wanted to check in on this. I am not a Decap expert, but I would be willing to help on this if I am able. Most of my development is in HTML, CSS, JavaScript. I've done quite a bit of React development but am not personally an expert. |
Beta Was this translation helpful? Give feedback.
-
There have been several support requests related to reducing the number of builds, by triggering builds in a cadence that is slower than on every commit. The free plan of some hosting providers, like Cloudflare Pages, is limited to a low number of builds. So, this proposal actually saves money by eliminating redundant builds. Also, there have been many support requests about missing features in the preview functionality. If your website has many custom widgets, a lot of double work is required to display content realistically in the preview window. The current proposal tries to address both concerns, by suggesting the addition of release tagging functionality.
A new main page "Releases" is proposed. On this page, the current version of your project is displayed. Below that, a form with a radiobutton group to indicate whether to bump the patch, minor or major version, and a submit button to update your project's version accordingly and push a tag like
release/{version}
to the latest commit. This will allow users to disable deployments triggered on the main branch and only deploy on new tags starting withrelease/*
.This functionality can easily be extended to facilitate separate preview deployments. Imagine a single prominent button to create a new preview by pushing a tag
release/{version}-alpha-{lastPreviewVersion + 1}
to the head of your main branch. This could be used to trigger a deployment to your preview domain, likepreview.yourwebsite.com
, based on the tag patternrelease/*alpha*
.Beta Was this translation helpful? Give feedback.
All reactions