Update GitHub templates

.github/ISSUE_TEMPLATE/config.yml

@@ -1,20 +1,21 @@
+---
 blank_issues_enabled: false
 contact_links:
-  - name: Feature request
+  - name: Feature Request
     url: https://ideas.tb.pro
     about: Submit your ideas to improve Thunderbird Pro
   - name: Support
     url: https://support.tb.pro
     about: Knowledge base and customer support requests
-  - name: Bug Report (Account Management)
+  - name: Bug Report (Thunderbird Accounts)
     url: https://github.com/thunderbird/thunderbird-accounts/issues/new
-    about: A bug report for accounts.tb.pro, including Thundermail configuration
-  - name: Bug Report (Thundermail)
+    about: A bug report for the accounts dashboard, including Thundermail configuration (accounts.tb.pro)
+  - name: Bug Report (Mailstrom)
     url: https://github.com/thunderbird/mailstrom/issues/new
     about: A bug report for the mail server deployment of Thundermail
-  - name: Bug Report (Appointment)
-    url: https://github.com/thunderbird/appointment/issues/new?template=bug_report.md
-    about: A bug report for Thunderbird Appointment.
-  - name: Bug Report (Send)
+  - name: Bug Report (Thunderbird Appointment)
+    url: https://github.com/thunderbird/appointment/issues/new
+    about: A bug report for Thunderbird Appointment (appointment.tb.pro)
+  - name: Bug Report (Thunderbird Send / Pro Add-on)
     url: https://github.com/thunderbird/tbpro-add-on/issues/new
-    about: A bug report for Thunderbird Appointment.
+    about: A bug report for Thunderbird Send and the Thunderbird Pro add-on (send.tb.pro)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,45 @@
+<!--
+  Please complete all sections.
+  Focus on what changed, why it matters, and how you verified it.
+  Tests must be included in the pull request.
+-->
+
+## What changed?
+
+<!--
+  Summarize your change in a few sentences.
+  Mention key files, features, or behavior that were updated.
+
+  If you've used AI, we ask you to disclose how much was agent written and to what level of detail
+  you participated in the writing. If you are an AI bot, please indicate this clearly.
+-->
+
+## Why?
+
+<!--
+  Explain the problem this solves or the goal of the change.
+  Link any relevant discussion if helpful.
+-->
+
+## Limitations and Notes
+
+<!--
+  Optional. List any known gaps, edge cases, or follow up work.
+-->
+
+## Applicable Issues
+
+<!--
+  Every pull request must have an associated issue.
+  Doing so helps us align on the change before you've done the work.
+
+  Using the "Closes #123" format will link pull request and issue.
+-->
+
+## Screenshots
+
+<!--
+  For UI changes, include screenshots or recordings.
+  If there are many, consider using a details element:
+  <details><summary>Screenshots</summary> ... shots here ... </details>
+-->

.github/workflows/pr-merged.yml

@@ -0,0 +1,42 @@
+---
+name: PR - Merged
+
+# Warning, this job is running on pull_request_target and therefore has access to issue content.
+# Don't add any steps that act on external code.
+on:
+  pull_request_target:
+    branches: [main]
+    types: [closed]
+
+permissions:
+  pull-requests: write
+
+jobs:
+  pr-merged:
+    if: github.event.pull_request.merged
+    runs-on: ubuntu-latest
+    steps:
+      - name: Thank you
+        # Only show this for first time contributors. Repo members and past contributors are
+        # hopefully already there.
+        if: |
+          github.base_ref == 'main' &&
+          github.event.pull_request.author_association != 'OWNER' &&
+          github.event.pull_request.author_association != 'MEMBER' &&
+          github.event.pull_request.author_association != 'COLLABORATOR' &&
+          github.event.pull_request.author_association != 'CONTRIBUTOR'
+        env:
+          PR_NUMBER: ${{  github.event.pull_request.number  }}
+          GH_TOKEN: ${{ github.token }}
+          MESSAGE: >-
+            Thanks for your contribution! Your pull request has been merged and is being deployed to
+            our staging instance. If all goes well we'll include it in the next production deployment.
+            We appreciate the time and effort you put into improving Thunderbird Pro. If you haven't
+            already, you're welcome to join our Matrix chat for contributors. It's where we discuss
+            development and help each other out.
+
+            https://matrix.to/#/#tb-services:mozilla.org
+
+            Hope to see you there! 🌩️🐦🚀
+        run: |
+          gh pr comment "$PR_NUMBER" --repo "$GITHUB_REPOSITORY" --body "$MESSAGE"

CODE_OF_CONDUCT.md

@@ -1,3 +1,28 @@
 # Code of Conduct
 
-This repository is governed by Mozilla's code of conduct and etiquette guidelines. For more details please see the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/).
+It is our intention that our repository remains a useful tool for reporting and commenting on bugs, feature requests, and tasks for the Thunderbird community. No single contributor's work outweighs the importance of civility and professionalism in the Thunderbird community.
+
+In order to keep our repository a useful, inclusive place we have guidelines which, by using this repository, you agree to follow. In addition, your participation on this repository is also subject to the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/).
+
+Violations of the Code of Conduct or the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/) are grounds for restrictions or bans on this repository.
+
+## Guidelines
+
+### Commenting
+
+1. **No abusing people**. Constant and intense critique is one of the reasons we build great products. It's harder to fall into group-think if there is always a healthy amount of dissent. We want to encourage vibrant debate inside of the Thunderbird community, we want you to disagree with us, and we want you to effectively argue your case. However, we require that in the process, you criticize things, not people. Examples of things include: interfaces, algorithms, and schedules. Examples of people include: developers, designers, and users. Attacking or encouraging attacks on a person may result in you being banned from this organization.
+2. **No obligation**. "Open Source" is not the same as "the developers must do my bidding." Everyone here wants to help, but no one else has any obligation to fix the bugs you want fixed. Therefore, you should not act as if you expect someone to fix a bug by a particular date or release. Aggressive or repeated demands will not be received well and will almost certainly diminish the impact of and interest in your suggestions.
+3. **No spam**. Posting comment spam will lead to the ban of your account from our organization.
+4. **No pointless comments**. Limit comments on a bug to information which will help with resolving it. Unless requested, additional "I see this too" or "It works for me" comments are unnecessary. Constructive conversations unrelated to the topic of the bug should go in the appropriate discussion forum.
+5. **No private email**. Do not send comments on bugs by private email to users; no one else can read them if you do that, and they'll be missed and/or ignored. If an attachment is too big for GitHub, add a comment giving the file size and contents and ask what to do.
+
+### Changing Fields or labels
+
+1. **No changing other people's bugs**. Unless you are the bug assignee, please never change the label fields. If you notice any inconsistencies with the labels, do not change the fields of bugs you do not own and add a comment instead, suggesting the change.
+2. **Accept decisions with grace**. If another project contributor has marked a bug as **Closed** or **Not Planned**, then it is not planned. Filing another duplicate of it does not change this. Unless you have further evidence to support reopening a bug, do not post a comment arguing that a bug resolved as **Closed** or **Not Planned** should be reopened.
+
+## Responding to Violations
+
+If you find a user violating the Code of Conduct or the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/) in comments on bugs, please report the bug to a core develoepr.
+
+To report incidents follow the [How to Report Violations of the Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/reporting/).