github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 20:41:29 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

[PR #1948] [MERGED] [PIQ-3] Add Github Actions to help manage issues and PRs #3244

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

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/1948
Author: @eliykat
Created: 6/10/2022
Status: ✅ Merged
Merged: 6/14/2022
Merged by: @eliykat

Base: master ← Head: bot-actions

📝 Commits (2)

  • 1d96310 Add automatic responses, community PR labeler, and stale Github Actions
  • fb3f6ae Remove pr-labeler

📊 Changes

2 files changed (+94 additions, -0 deletions)

View changed files

➕ .github/workflows/automatic-issue-responses.yml (+64 -0)
➕ .github/workflows/stale-bot.yml (+30 -0)

📄 Description

Type of change

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

Objective

Add the "automatic response" and "close stale issues/PRs" workflows from https://github.com/bitwarden/server/pull/1981. For info on how this works, see https://bitwarden.atlassian.net/wiki/spaces/PIQ/pages/195657879/Github+Actions+Issues+and+PRs.

I've removed the community-pr labeler because it won't run on forked repos, so I need to rethink that.

Code changes

  • file.ext: Description of what was changed and why

Screenshots

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/1948 **Author:** [@eliykat](https://github.com/eliykat) **Created:** 6/10/2022 **Status:** ✅ Merged **Merged:** 6/14/2022 **Merged by:** [@eliykat](https://github.com/eliykat) **Base:** `master` ← **Head:** `bot-actions` --- ### 📝 Commits (2) - [`1d96310`](https://github.com/bitwarden/android/commit/1d963107f03e37eddc0772a3ad23b48142f91152) Add automatic responses, community PR labeler, and stale Github Actions - [`fb3f6ae`](https://github.com/bitwarden/android/commit/fb3f6ae78552155d23399972aa51181875123085) Remove pr-labeler ### 📊 Changes **2 files changed** (+94 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/automatic-issue-responses.yml` (+64 -0) ➕ `.github/workflows/stale-bot.yml` (+30 -0) </details> ### 📄 Description ## Type of change - [ ] Bug fix - [ ] New feature development - [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc) - [ ] Build/deploy pipeline (DevOps) - [x] Other ## Objective <!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding--> Add the "automatic response" and "close stale issues/PRs" workflows from https://github.com/bitwarden/server/pull/1981. For info on how this works, see https://bitwarden.atlassian.net/wiki/spaces/PIQ/pages/195657879/Github+Actions+Issues+and+PRs. I've removed the community-pr labeler because it won't run on forked repos, so I need to rethink that. ## 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--> * **file.ext:** Description of what was changed and why ## Screenshots <!--Required for any UI changes. Delete if not applicable--> ## 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) --- <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:12 -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#3244
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?