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

feat(content-distribution): post status on create #189

Merged
merged 22 commits into from
Jan 20, 2025

Conversation

miguelpeixe
Copy link
Member

@miguelpeixe miguelpeixe commented Jan 17, 2025

1208510338230630-as-1209168371395424
p1737121608239039-slack-C055SRT7WN4

Support configuring the post status on distribution. This should only take effect when creating the post.

image image image

Testing

  1. Distribute a post without changing the status and confirm it's distributed as a draft.
  2. Distribute a post changing the status to "Published" and confirm it's distributed as published.
  3. Do the same via CLI and confirm it also reflects the status:
newspack network distribute post {post_id} --sites=https://node1.local --status_on_create=publish

@miguelpeixe miguelpeixe requested a review from a team as a code owner January 17, 2025 15:45
@miguelpeixe miguelpeixe self-assigned this Jan 17, 2025
Base automatically changed from fix/content-distribution-editor-outgoing-post to trunk January 20, 2025 15:49
@miguelpeixe miguelpeixe requested a review from naxoc January 20, 2025 18:18
Copy link
Member

@naxoc naxoc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 👍

Added a couple of small comments, but feel free to merge once you are done with those :)

@@ -28,19 +28,16 @@
}

.editor-sidebar:not(#newspack-network-incoming-post\:newspack-network-content-distribution-panel, #edit-post\:document) {
@include grey-out-outer;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this one might also overwrite #193

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤦 I did a very bad job fixing conflicts, sorry about that!

Fixed in 8ed2220

@@ -0,0 +1,16 @@
/**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor: but why is it drafts plural? Should it not be singular?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. Thanks!

@miguelpeixe miguelpeixe requested a review from naxoc January 20, 2025 20:37
@miguelpeixe miguelpeixe merged commit 1ad3e0c into trunk Jan 20, 2025
4 checks passed
Copy link

Hey @miguelpeixe, good job getting this PR merged! 🎉

Now, the needs-changelog label has been added to it.

Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label.

If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label.

Thank you! ❤️

@miguelpeixe miguelpeixe deleted the feat/content-distribution-status-on-create branch January 20, 2025 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants