Skip to content

Conversation

@ashleysmithTTD
Copy link
Contributor

No description provided.

context: examples/google-secure-signals-integration/client_side
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do we still want to couple all of these between a release file for each and then a publish file for all three together? Or do we want to make each one a separate publish yml file? This can be done now or later.

Also side note: we should probably rename the "standard" secure signals site to client-server which we can clean up later also

Copy link
Contributor

Choose a reason for hiding this comment

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

As much as it seems wasteful to have three separate files, I think it makes sense to do that. We won't always be (rarely be?) modifying all of them at once so creating new versions/images with no changes seems bad. what do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed

@ashleysmithTTD ashleysmithTTD merged commit 2f9330c into main Feb 3, 2025
3 checks passed
@ashleysmithTTD ashleysmithTTD deleted the ans-UID2-4749-create-uid2-client-side-secure-signals-page branch February 3, 2025 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants