Add email integration working with secrets #9

Merged
notplants merged 1 commits from email-integration into main 2025-11-18 17:17:53 +00:00
Owner

Continuing with all the same patterns as before, just added settings and secrets for email integration (tested & working)

Also found a nice interface in my IDE (pycharm) I'd never seen before for quickly and graphically squashing commits ... so less git messiness this time

Continuing with all the same patterns as before, just added settings and secrets for email integration (tested & working) Also found a nice interface in my IDE (pycharm) I'd never seen before for quickly and graphically squashing commits ... so less git messiness this time
notplants added 1 commit 2025-11-17 17:48:36 +00:00
Author
Owner

This will complete this issue: #1

This will complete this issue: https://git.coopcloud.tech/coop-cloud/lasuite-docs/issues/1
Author
Owner

@3wordchant I'm also not totally clear on the protocol for merging PRs here with coop cloud recipes.

Is there a defined maintainer for each recipe?

I'm always happy to receive a code review, even retrospectively on a merged PR, if you have the spoons. But should I just merge PRs optimistically if you are not actively maintaining/hosting this recipe rn?

@3wordchant I'm also not totally clear on the protocol for merging PRs here with coop cloud recipes. Is there a defined maintainer for each recipe? I'm always happy to receive a code review, even retrospectively on a merged PR, if you have the spoons. But should I just merge PRs optimistically if you are not actively maintaining/hosting this recipe rn?
Owner

Looks great overall!

Ideally maybe a release note about the secrets change… but practically I haven't heard of anyone except Autonomic using this recipe yet, so probably not required.

Is there a defined maintainer for each recipe?

Yes! There should be! Rollout is proceeding slowly.

There is no maintainer for this recipe yet

image.png

I'm also not totally clear on the protocol for merging PRs here with coop cloud recipes.

I think in cases where there is a maintainer, there's been discussion of making so only the maintainer(s) can merge PRs. The process is fairly undefined otherwise.

But should I just merge PRs optimistically if you are not actively maintaining/hosting this recipe rn?

Yes.

Looks great overall! Ideally maybe a release note about the secrets change… but practically I haven't heard of anyone except Autonomic using this recipe yet, so probably not required. > Is there a defined maintainer for each recipe? Yes! [There should be!](https://docs.coopcloud.tech/federation/resolutions/passed/025/) Rollout is proceeding slowly. There is no maintainer for this recipe yet ![image.png](/attachments/bac4554d-2dd5-4118-abff-00a878df76e2) > I'm also not totally clear on the protocol for merging PRs here with coop cloud recipes. I think in cases where there is a maintainer, there's been discussion of making so only the maintainer(s) can merge PRs. The process is fairly undefined otherwise. > But should I just merge PRs optimistically if you are not actively maintaining/hosting this recipe rn? Yes.
413 KiB
notplants merged commit 16c68c085b into main 2025-11-18 17:17:53 +00:00
notplants deleted branch email-integration 2025-11-18 17:17:57 +00:00
Sign in to join this conversation.
No description provided.