github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 03:33:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[PR #4294] [MERGED] [PM-14879] Release Branch creation workflow #4840

New Issue
Closed
opened 2025-11-26 23:50:29 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 23:50:29 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/4294
Author: @vvolkgang
Created: 11/12/2024
Status: ✅ Merged
Merged: 11/13/2024
Merged by: @vvolkgang

Base: main ← Head: cut-release-branch

📝 Commits (2)

  • 295fbc8 Add workflow to create release branches
  • ef4f3c1 Use git switch instead of checkout

📊 Changes

1 file changed (+56 additions, -0 deletions)

View changed files

➕ .github/workflows/release-branch.yml (+56 -0)

📄 Description

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-14879

📔 Objective

Adds workflow to create release branches, supports RC and Hotfix:

  1. RC branches are created with the following naming pattern: release/{YYY.MM}-rc{build_number}, e.g. release/2024.11-rc5. Date prefix can be removed by a workflow input, in that case it would create a release/rc5.
  2. Hotfix branches are created using the last release tag, e.g. hotfix-v2024.11.4

Running this workflow with Hotfix multiple times won't fail, although logs are slightly different - we don't receive remote logs

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/4294 **Author:** [@vvolkgang](https://github.com/vvolkgang) **Created:** 11/12/2024 **Status:** ✅ Merged **Merged:** 11/13/2024 **Merged by:** [@vvolkgang](https://github.com/vvolkgang) **Base:** `main` ← **Head:** `cut-release-branch` --- ### 📝 Commits (2) - [`295fbc8`](https://github.com/bitwarden/android/commit/295fbc8ebe5cbd94e9cb500f62c3fba91c54d21b) Add workflow to create release branches - [`ef4f3c1`](https://github.com/bitwarden/android/commit/ef4f3c18038ef07e29046b5933899f7ab79af05b) Use git switch instead of checkout ### 📊 Changes **1 file changed** (+56 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/release-branch.yml` (+56 -0) </details> ### 📄 Description ## 🎟️ Tracking https://bitwarden.atlassian.net/browse/PM-14879 ## 📔 Objective Adds workflow to create release branches, supports RC and Hotfix: 1. RC branches are created with the following naming pattern: `release/{YYY.MM}-rc{build_number}`, e.g. `release/2024.11-rc5`. Date prefix can be removed by a workflow input, in that case it would create a `release/rc5`. 2. Hotfix branches are created using the last release tag, e.g. `hotfix-v2024.11.4` Running this workflow with `Hotfix` multiple times won't fail, although logs are slightly different - we don't receive remote logs ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-26 23:50:29 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#4840
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?