Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task/1943 refreshing transactional send journeys changes the lastmodified timestamp and we should re download them #1983

Conversation

JoernBerkefeld
Copy link
Contributor

@JoernBerkefeld JoernBerkefeld commented Jan 13, 2025

PR details

What changes did you make? (Give an overview)

Further details (optional)

...

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • test scripts updated
  • Wiki updated (if applicable)

Copy link

Coverage Report

Commit:2dacb7f
Base: develop@47bfc31

Type Base This PR
Total Statements Coverage  70.56%  70.62%  (+0.06%)
Total Branches Coverage  69.28%  69.35%  (+0.07%)
Total Functions Coverage  83.28%  83.3%  (+0.02%)
Total Lines Coverage  70.56%  70.62%  (+0.06%)
Details (changed files):
File Statements Branches Functions Lines
lib/metadataTypes/Journey.js  66.38%  66.1%  91.66%  66.38%

@JoernBerkefeld JoernBerkefeld merged commit 4e15809 into develop Jan 13, 2025
10 of 13 checks passed
@JoernBerkefeld JoernBerkefeld deleted the task/1943-refreshing-transactional-send-journeys-changes-the-lastmodified-timestamp-and-we-should-re-download-them branch January 13, 2025 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c/journey COMPONENT c/transactionalEmail chore Jira issue-type "Task"
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TASK] refresh transactional send journeys changes the lastmodified timestamp and we should re-download them
1 participant