morgan pushed to branch tor-browser-128.7.0esr-14.5-1 at The Tor Project / 
Applications / Tor Browser


Commits:
e01fb03c by Morgan at 2025-02-13T16:26:45+00:00
fixup! Adding issue and merge request templates

add issue template for mozilla uplifts and tweak MR template to signal to 
merger an uplift issue should be created after merge

- - - - -


2 changed files:

- + .gitlab/issue_templates/Uplift.md
- .gitlab/merge_request_templates/default.md


Changes:

=====================================
.gitlab/issue_templates/Uplift.md
=====================================
@@ -0,0 +1,19 @@
+<!--
+Title:
+    Uplift tor-browser#12345: Title of Issue
+-->
+
+# Uplift Patchset
+
+## Gitlab Issue(s)
+- tor-browser#12345
+- mullvad-browser#12345
+
+## Upstream Mozilla Issue(s):
+- https://bugzilla.mozilla.org/show_bug.cgi?id=12345
+
+## Notes
+
+<!-- whatever additional info, context, etc that would be helpful for 
uplifting -->
+
+/label ~"Apps::Type::Uplift"


=====================================
.gitlab/merge_request_templates/default.md
=====================================
@@ -48,6 +48,9 @@
 - [ ] **Localization**: typos and other localization changes that should be 
also in the release branch
 - [ ] **Other**: please explain
 
+### Uplifting
+- [ ] Patchset is a candidate for uplift to Firefox
+
 ### Issue Tracking
 - [ ] Link resolved issues with appropriate [Release Prep 
issue](https://gitlab.torproject.org/groups/tpo/applications/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=Release%20Prep&first_page_size=20)
 for changelog generation
 



View it on GitLab: 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/commit/e01fb03c9e53a3684e4027a3a9acf628ce0e259c

-- 
View it on GitLab: 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/commit/e01fb03c9e53a3684e4027a3a9acf628ce0e259c
You're receiving this email because of your account on gitlab.torproject.org.


_______________________________________________
tbb-commits mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to