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

[PR #2022] [MERGED] [ENG-71] Add Github deployment to release pipeline. #3298

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

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/2022
Author: @trmartin4
Created: 8/1/2022
Status: ✅ Merged
Merged: 8/4/2022
Merged by: @trmartin4

Base: master ← Head: ENG-71-add-deployment

📝 Commits (5)

  • a756bb9 Added Github deployment to release pipeline.
  • ffb3446 Added explicit expression syntax
  • a9ca905 Added explicit expression syntax
  • 924ec30 Added initial-status
  • 7e5edd4 Removed in_progress update since it's set on initial status

📊 Changes

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

View changed files

📝 .github/workflows/release.yml (+27 -0)

📄 Description

Type of change

  • Bug fix
  • New feature development
  • Tech debt (refactoring, code cleanup, dependency upgrades, etc)
  • Build/deploy pipeline (DevOps)
  • Other

Objective

In order to track which Jira issues are included in each deployment, we need to tie the release pipeline to Github deployments, which the Github for Jira integration will then tie to Jira deployments.

Code changes

  • release.yml Added workflow steps to create a Github deployment and update the status to success or failure based on the job success or failure.

Before you submit

  • I have checked for formatting errors (dotnet tool run dotnet-format --check) (required)
  • I have added unit tests where it makes sense to do so (encouraged but not required)
  • This change requires a documentation update (notify the documentation team)
  • This change has particular deployment requirements (notify the DevOps team)

🔄 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/2022 **Author:** [@trmartin4](https://github.com/trmartin4) **Created:** 8/1/2022 **Status:** ✅ Merged **Merged:** 8/4/2022 **Merged by:** [@trmartin4](https://github.com/trmartin4) **Base:** `master` ← **Head:** `ENG-71-add-deployment` --- ### 📝 Commits (5) - [`a756bb9`](https://github.com/bitwarden/android/commit/a756bb91fcbbf63b480138f76a7b75e584b4ce6a) Added Github deployment to release pipeline. - [`ffb3446`](https://github.com/bitwarden/android/commit/ffb3446e37cca83bdcd145d7e8ce5ef16f94baad) Added explicit expression syntax - [`a9ca905`](https://github.com/bitwarden/android/commit/a9ca905c5d4932d5c81b3de51a9433862bb9d749) Added explicit expression syntax - [`924ec30`](https://github.com/bitwarden/android/commit/924ec30bfc6a43bf4e0862bc67892fd2b409fec1) Added initial-status - [`7e5edd4`](https://github.com/bitwarden/android/commit/7e5edd43ed3977dcf26f5714309908fdc0d35e41) Removed in_progress update since it's set on initial status ### 📊 Changes **1 file changed** (+27 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+27 -0) </details> ### 📄 Description ## Type of change - [ ] Bug fix - [ ] New feature development - [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc) - [X] Build/deploy pipeline (DevOps) - [ ] Other ## Objective In order to track which Jira issues are included in each deployment, we need to tie the release pipeline to Github deployments, which the Github for Jira integration will then tie to Jira deployments. ## Code changes <!--Explain the changes you've made to each file or major component. This should help the reviewer understand your changes--> <!--Also refer to any related changes or PRs in other repositories--> * **[release.yml](https://github.com/bitwarden/mobile/compare/ENG-71-add-deployment?expand=1#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34)** Added workflow steps to create a Github deployment and update the status to success or failure based on the job success or failure. ## Before you submit - [ ] I have checked for formatting errors (`dotnet tool run dotnet-format --check`) (required) - [ ] I have added **unit tests** where it makes sense to do so (encouraged but not required) - [ ] This change requires a **documentation update** (notify the documentation team) - [X] This change has particular **deployment requirements** (notify the DevOps team) --- <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:30:53 -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#3298
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?