fix: make welcome email generic #538
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* main: fix: allow user in bank transaction to be blank in forms (TampereHacklab#539) Korjattu assertti Feature/matrix invites (TampereHacklab#488) fix ci (TampereHacklab#533) Update account_deactivated_and_marked_for_deletion.txt (TampereHacklab#500) Bump Python version to 3.11 used in Debian 12 (TampereHacklab#523)
Sandplum
added a commit
that referenced
this pull request
Feb 4, 2025
Following the style of PR #538 welcome email
|
I'm merging this and will do another pr for translations in a moment |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I suggest that we make this email really generic (more generic than suggested in the linked issue), since we can't be sure that any given association using mulysa uses a door system, matrix or what kind of meetings they have.
fixes #505