|
| 1 | +name: "Release Request" |
| 2 | +description: "Request a production deployment by specifying the chat function, changes, target branch, and version bump." |
| 3 | +title: "Release Request" |
| 4 | +labels: |
| 5 | + - release |
| 6 | + - deployment |
| 7 | +assignees: [] |
| 8 | +body: |
| 9 | + - type: markdown |
| 10 | + attributes: |
| 11 | + value: | |
| 12 | + ## How this works |
| 13 | +
|
| 14 | + 1. **Fill in this form** (description of changes, branch, version bump). Do not submit yet. |
| 15 | + 2. **Scroll to the bottom and open the *Production deploy* workflow link in a new tab** — it disappears after you submit this form, so you need it open beforehand. |
| 16 | + 3. **Submit this issue** to record the release request and start the workflow. |
| 17 | + 4. The workflow redeploys staging, then pauses on the **manual approval gate** — a Lambda Feedback admin reviews this issue and approves the run there. |
| 18 | + 5. Once approved, a `vX.Y.Z` git tag and GitHub Release are created and the function is deployed to production. |
| 19 | + 6. Once the release is live, post a comment on this issue with the URL of the new GitHub Release (e.g. `https://github.com/<org>/<repo>/releases/tag/vX.Y.Z`) and then close the issue. This helps us keep track of which releases correspond to which requests. |
| 20 | +
|
| 21 | + - type: textarea |
| 22 | + id: description_of_changes |
| 23 | + attributes: |
| 24 | + label: Description of changes |
| 25 | + description: "Summarize what is changing and why. Include links to PRs, issues, or changelogs." |
| 26 | + placeholder: | |
| 27 | + - What changed: |
| 28 | + - Why: |
| 29 | + - Related PRs/Issues: #123, #456 |
| 30 | + render: markdown |
| 31 | + validations: |
| 32 | + required: true |
| 33 | + |
| 34 | + - type: input |
| 35 | + id: branch_to_deploy |
| 36 | + attributes: |
| 37 | + label: Branch to deploy |
| 38 | + description: | |
| 39 | + Specify the branch to deploy. |
| 40 | + placeholder: "e.g., main" |
| 41 | + validations: |
| 42 | + required: true |
| 43 | + |
| 44 | + - type: dropdown |
| 45 | + id: version-bump |
| 46 | + attributes: |
| 47 | + label: "🚀 What kind of update is this?" |
| 48 | + description: "Tell us how significant this change is. This helps us set the correct new version number." |
| 49 | + options: |
| 50 | + - "Patch: A small fix for a bug. It won't break anything for existing users. (e.g., 1.2.3 ➔ 1.2.4)" |
| 51 | + - "Minor: Adds a new feature, but doesn't change how existing ones work. A safe update. (e.g., 1.2.3 ➔ 1.3.0)" |
| 52 | + - "Major: A big change that alters existing features. Users may need to update their work to adapt. (e.g., 1.2.3 ➔ 2.0.0)" |
| 53 | + default: 0 |
| 54 | + validations: |
| 55 | + required: true |
| 56 | + |
| 57 | + - type: markdown |
| 58 | + attributes: |
| 59 | + value: | |
| 60 | + --- |
| 61 | + ### ⚡ Click the Link Below to Run the Workflow |
| 62 | +
|
| 63 | + ⚠️ Open the workflow page in a new tab before submitting the issue, because the link to the workflow run page will disappear after submission. |
| 64 | +
|
| 65 | + Clicking the link will take you to the Actions page. You will need to click the **"Run workflow"** button there to start the process. |
| 66 | + Select the same branch and version bump type you entered in this form, then click the green **"Run workflow"** button. |
| 67 | +
|
| 68 | +
|
| 69 | + ## [➡️ Go to Workflow Run Page](../actions/workflows/production-deploy.yml) |
0 commit comments