github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-11 17:16:20 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[PR #1994] [MERGED] Add publish options to release workflow #83118

New Issue
Closed
opened 2026-05-22 16:35:26 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-22 16:35:26 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/1994
Author: @mimartin12
Created: 7/14/2022
Status: ✅ Merged
Merged: 7/15/2022
Merged by: @mimartin12

Base: master ← Head: DEVOPS-871-add-job-disabling-to-the-release-workflows-with-store-deployments

📝 Commits (2)

📊 Changes

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

View changed files

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

📄 Description

Type of change

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

Objective

At times, we find that we need to re-run a workflow to publish to an app store. We need the ability to have more selection over the specific stores. This adds a boolean input for the f-droid step, which defaults to true.

Code changes

  • .github/workflows/release.yml: Add input option for f-droid release.

Screenshots

image

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/1994 **Author:** [@mimartin12](https://github.com/mimartin12) **Created:** 7/14/2022 **Status:** ✅ Merged **Merged:** 7/15/2022 **Merged by:** [@mimartin12](https://github.com/mimartin12) **Base:** `master` ← **Head:** `DEVOPS-871-add-job-disabling-to-the-release-workflows-with-store-deployments` --- ### 📝 Commits (2) - [`a272fa0`](https://github.com/bitwarden/android/commit/a272fa0ee06159f7bf94e9d82b26dd51cda53ac0) Add publish inputs for f-droid - [`b3dca49`](https://github.com/bitwarden/android/commit/b3dca49319bf472ca83f9c68985674431f7065b7) Update if: logic ### 📊 Changes **1 file changed** (+6 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+6 -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 <!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding--> At times, we find that we need to re-run a workflow to publish to an app store. We need the ability to have more selection over the specific stores. This adds a boolean input for the f-droid step, which defaults to true. ## 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--> * **.github/workflows/release.yml:** Add input option for f-droid release. ## Screenshots <!--Required for any UI changes. Delete if not applicable--> ![image](https://user-images.githubusercontent.com/77340197/179073332-27f5a0a7-8155-41ae-8f63-a9902753481b.png) ## Before you submit - [X] 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 2026-05-22 16:35:26 -05: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#83118
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?