snapshot of https://github.com/RocketChat/Rocket.Chat.git (develop, 2026-09-16; blobs > 131072B omitted)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,59 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+<!-- 
+
+Please see our guide for opening issues: https://developer.rocket.chat/rocket.chat/contribute-to-rocket.chat/ways-to-contribute/report-bugs
+
+If you have questions or are looking for help/support please see: https://rocket.chat/docs/getting-support
+
+If you are experiencing a bug please search our issues to be sure it is not already present: https://github.com/RocketChat/Rocket.Chat/issues
+
+-->
+
+### Description:
+
+<!-- A clear and concise description of what the bug is. -->
+
+### Steps to reproduce:
+
+1. <!-- Go to '...' -->
+2. <!-- Click on '....' -->
+3. <!-- and so on... -->
+
+### Expected behavior:
+
+<!-- What you expect to happen -->
+
+### Actual behavior:
+
+<!-- What actually happens with SCREENSHOT, if applicable -->
+
+### Server Setup Information:
+
+- Version of Rocket.Chat Server: 
+- License Type:
+- Number of Users: 
+- Operating System: 
+- Deployment Method: <!-- snap/docker/tar/etc -->
+- Number of Running Instances: 
+- DB Replicaset Oplog: 
+- NodeJS Version: 
+- MongoDB Version:
+
+### Client Setup Information
+
+- Desktop App or Browser Version:
+- Operating System:
+
+### Additional context
+
+<!-- Add any other context about the problem here. -->
+
+### Relevant logs:
+
+<!-- Logs from both SERVER and BROWSER -->
+<!-- For more information about collecting logs please see: https://rocket.chat/docs/contributing/reporting-issues#gathering-logs -->

.github/ISSUE_TEMPLATE/release.md

@@ -0,0 +1,59 @@
+---
+name: Release
+about: Internal release checklist template
+
+---
+
+# Release {version}
+We are releasing a new version, this issue will keep track of the progress between the first release candidate (20th of each month) to the final release (27th of each month).
+
+Beginning on the 20th of each month, we will start the release process which ends 7 days later (the 27th). During this period of time, we will enter a "Feature Freeze". This Feature Freeze means that we will only be merging pull requests which fix bugs and not ones that add new features.
+
+When you find a bug that is a regression, please open a new issue and link it to this one.
+
+
+## Before Release - Preparation - 1 business day before the day 20th
+- [x] Create the issue to track the release progress
+- [ ] Define the highlights from release PRs as a suggestion to be included on Blog Post <!-- link to the website's issue -->
+- [ ] Talk to the Marketing Team about starting the release Blog Post
+- [ ] Talk to the Documentation Team about ensuring the Docs are up to date and all pull requests are merged
+- [ ] Sync translations from [LingoHub](https://translate.lingohub.com/rocketchat/rocket-dot-chat/dashboard)
+
+## Release Candidate 1 - On the 20th
+- [ ] Execute action `Release Candidate` via [Houston CLI](https://github.com/RocketChat/Rocket.Chat.Houston) (`houston release`)
+- [ ] Check if `release-candidate` branch was published
+- [ ] Check if the tag was published and contains the history
+- [ ] Ensure the build is passing on [CircleCI](https://circleci.com/gh/RocketChat/Rocket.Chat)
+- [ ] Ensure the image was sent to [Docker Hub](https://hub.docker.com/r/rocketchat/rocket.chat/tags/)
+
+<!-- Copy following block for next release candidates
+## Release Candidate {release-candidate-version} - On the {day}
+- [ ] Execute action `Release Candidate` via [Houston CLI](https://github.com/RocketChat/Rocket.Chat.Houston) (`houston release`)
+- [ ] Check if `release-candidate` branch was published
+- [ ] Check if the tag was published and contains the history
+- [ ] Ensure the build is passing on [CircleCI](https://circleci.com/gh/RocketChat/Rocket.Chat)
+- [ ] Ensure the image was sent to [Docker Hub](https://hub.docker.com/r/rocketchat/rocket.chat/tags/)
+-->
+
+## Final Release - On the 27th
+- [ ] Execute action `Final Release` via [Houston CLI](https://github.com/RocketChat/Rocket.Chat.Houston) (`houston release`)
+- [ ] Check if `release-{version}` branch was published
+- [ ] Check if the release was created as **draft** and contains the history
+- [ ] Check if the release Pull Request was created and contains the history
+- [ ] Ensure the **Pull Request** build is passing on [CircleCI](https://circleci.com/gh/RocketChat/Rocket.Chat)
+- [ ] When the build is passing ask for Pull Request approval
+- [ ] When approved, merge it!
+- [ ] Ensure the **Tag** build is passing on [CircleCI](https://circleci.com/gh/RocketChat/Rocket.Chat)
+- [ ] Ensure the image was sent to [Docker Hub](https://hub.docker.com/r/rocketchat/rocket.chat/tags/)
+- [ ] After all edit the release/tag and publish it
+
+## After Release - Conclusion - 1 business day after the 27th
+- [ ] Ensure all of the related issues were closed
+- [ ] Determine if all of the related issues were correctly assigned to this version's milestone
+- [ ] Get an update from Marketing Team about the release of Blog Post
+- [ ] Check with the Documentation Team about the Docs release
+- [ ] Sync develop
+  - [ ] Execute action `Develop Sync` via [Houston CLI](https://github.com/RocketChat/Rocket.Chat.Houston) (`houston release`)
+  - [ ] Ensure the **Pull Request** build is passing on [CircleCI](https://circleci.com/gh/RocketChat/Rocket.Chat)
+  - [ ] When the build has passed, ask for approval and wait
+  - [ ] Merge Sync PR