Skip to content

Conversation

@nextcloud-bot
Copy link
Member

@nextcloud-bot nextcloud-bot commented Jan 14, 2026

Nextcloud 33

server

circles

files_pdfviewer

notifications

serverinfo

text

Pending PRs:


  • ⚠: conflicts detected
  • ✅: approved
  • 🔁: changes requested

Signed-off-by: Worker Builder <[email protected]>
@nextcloud-bot nextcloud-bot requested a review from a team as a code owner January 14, 2026 14:08
@nextcloud-bot nextcloud-bot added this to the Nextcloud 33 milestone Jan 14, 2026
@nextcloud-bot nextcloud-bot requested review from Altahrim, ArtificialOwl and salmart-dev and removed request for a team January 14, 2026 14:08
@nextcloud-bot nextcloud-bot added the 3. to review Waiting for reviews label Jan 14, 2026
@blizzz blizzz merged commit 748206f into master Jan 15, 2026
188 of 196 checks passed
@blizzz blizzz deleted the release/33.0.0_beta_4 branch January 15, 2026 22:24
@cherti
Copy link

cherti commented Jan 15, 2026

Is it possible to not be included in every beta PR if there is no intention to merge the PR I am listed with here anyways? Over a dozen e-mails by now, none of which are actionable or relevant feel unnecessarily spammy. Thank you.

@AndyScherzinger
Copy link
Member

@cherti the script grabs any PR assigned to the v33 milestone. So yes, the easiest way is to I assign the milestone on your PRs, than the script won't catch them and won't mention you.
Hope this helps 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants